Methods for efficient resource usage between cooperative vehicles

ABSTRACT

Methods, systems, and apparatuses for sidelink communication are disclosed. A WTRU may receive a first SCI element from a second WTRU within a group. The WTRU may receive a first RCI element within a first set of resources scheduled by the first SCI. The first RCI may include information about which WTRU in the group is scheduled to use a second set of resources. The WTRU may determine, based on the first RCI, that one or more subresources within the second set of resources are available. The WTRU may transmit data in the one or more subresources. The first SCI and the first RCI may be received in a first reservation period and the one or more subresources may be in a second reservation period.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/651,974 filed Apr. 3, 2018, U.S. Provisional Application No.62/668,322 filed May 8, 2018, and U.S. Provisional Application No.62/735,982 filed Sep. 25, 2018, the contents of which are incorporatedherein by reference.

BACKGROUND

Vehicular (“V2X”) communication is a mode of communication in whichwireless transmit/receive units (WTRUs) may communicate with each otherdirectly. While in coverage, WTRUs may receive assistance from a networkto start transmitting and receiving V2X messages. While out of coverage,WTRUs may use one or more pre-configured parameters to starttransmitting and receiving V2X messages.

SUMMARY

Methods, systems, and apparatuses for sidelink communication aredisclosed. A WTRU may receive a first SCI element from a second WTRUwithin a group. The WTRU may receive a first RCI element within a firstset of resources scheduled by the first SCI. The first RCI may includeinformation about which WTRU in the group is scheduled to use a secondset of resources. The WTRU may determine, based on the first RCI, thatone or more subresources within the second set of resources areavailable. The WTRU may transmit data in the one or more subresources.The first SCI and the first RCI may be received in a first reservationperiod and the one or more subresources may be in a second reservationperiod.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description,given by way of example in conjunction with the accompanying drawings,wherein like reference numerals in the figures indicate like elements,and wherein:

FIG. 1A is a system diagram illustrating an example communicationssystem in which one or more disclosed embodiments may be implemented;

FIG. 1B is a system diagram illustrating an example wirelesstransmit/receive unit (WTRU) that may be used within the communicationssystem illustrated in FIG. 1A according to an embodiment;

FIG. 10 is a system diagram illustrating an example radio access network(RAN) and an example core network (CN) that may be used within thecommunications system illustrated in FIG. 1A according to an embodiment;

FIG. 1D is a system diagram illustrating a further example RAN and afurther example CN that may be used within the communications systemillustrated in FIG. 1A according to an embodiment;

FIG. 2 is a diagram illustrating a first method of group reservationusing subresource coordination;

FIG. 3 is a diagram illustrating a second method of group reservationusing subresource coordination;

FIG. 4 is a diagram illustrating a method of reserving contention basedresources; and

FIG. 5 is a flowchart illustrating the first method of group reservationusing subresource coordination.

DETAILED DESCRIPTION

FIG. 1A is a diagram illustrating an example communications system 100in which one or more disclosed embodiments may be implemented. Thecommunications system 100 may be a multiple access system that providescontent, such as voice, data, video, messaging, broadcast, etc., tomultiple wireless users. The communications system 100 may enablemultiple wireless users to access such content through the sharing ofsystem resources, including wireless bandwidth. For example, thecommunications systems 100 may employ one or more channel accessmethods, such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA),orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tailunique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S-OFDM),unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bankmulticarrier (FBMC), and the like.

As shown in FIG. 1A, the communications system 100 may include wirelesstransmit/receive units (WTRUs) 102 a, 102 b, 102 c, 102 d, a radioaccess network (RAN) 104, a core network (CN) 106, a public switchedtelephone network (PSTN) 108, the Internet 110, and other networks 112,though it will be appreciated that the disclosed embodiments contemplateany number of WTRUs, base stations, networks, and/or network elements.Each of the WTRUs 102 a, 102 b, 102 c, 102 d may be any type of deviceconfigured to operate and/or communicate in a wireless environment. Byway of example, the WTRUs 102 a, 102 b, 102 c, 102 d, any of which maybe referred to as a station (STA), may be configured to transmit and/orreceive wireless signals and may include a user equipment (UE), a mobilestation, a fixed or mobile subscriber unit, a subscription-based unit, apager, a cellular telephone, a personal digital assistant (PDA), asmartphone, a laptop, a netbook, a personal computer, a wireless sensor,a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watchor other wearable, a head-mounted display (HMD), a vehicle, a drone, amedical device and applications (e.g., remote surgery), an industrialdevice and applications (e.g., a robot and/or other wireless devicesoperating in an industrial and/or an automated processing chaincontexts), a consumer electronics device, a device operating oncommercial and/or industrial wireless networks, and the like. Any of theWTRUs 102 a, 102 b, 102 c and 102 d may be interchangeably referred toas a UE.

The communications systems 100 may also include a base station 114 aand/or a base station 114 b. Each of the base stations 114 a, 114 b maybe any type of device configured to wirelessly interface with at leastone of the WTRUs 102 a, 102 b, 102 c, 102 d to facilitate access to oneor more communication networks, such as the CN 106, the Internet 110,and/or the other networks 112. By way of example, the base stations 114a, 114 b may be a base transceiver station (BTS), a NodeB, an eNode B(eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as agNode B (gNB), a new radio (NR) NodeB, a site controller, an accesspoint (AP), a wireless router, and the like. While the base stations 114a, 114 b are each depicted as a single element, it will be appreciatedthat the base stations 114 a, 114 b may include any number ofinterconnected base stations and/or network elements.

The base station 114 a may be part of the RAN 104, which may alsoinclude other base stations and/or network elements (not shown), such asa base station controller (BSC), a radio network controller (RNC), relaynodes, and the like. The base station 114 a and/or the base station 114b may be configured to transmit and/or receive wireless signals on oneor more carrier frequencies, which may be referred to as a cell (notshown). These frequencies may be in licensed spectrum, unlicensedspectrum, or a combination of licensed and unlicensed spectrum. A cellmay provide coverage for a wireless service to a specific geographicalarea that may be relatively fixed or that may change over time. The cellmay further be divided into cell sectors. For example, the cellassociated with the base station 114 a may be divided into threesectors. Thus, in one embodiment, the base station 114 a may includethree transceivers, i.e., one for each sector of the cell. In anembodiment, the base station 114 a may employ multiple-input multipleoutput (MIMO) technology and may utilize multiple transceivers for eachsector of the cell. For example, beamforming may be used to transmitand/or receive signals in desired spatial directions.

The base stations 114 a, 114 b may communicate with one or more of theWTRUs 102 a, 102 b, 102 c, 102 d over an air interface 116, which may beany suitable wireless communication link (e.g., radio frequency (RF),microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet(UV), visible light, etc.). The air interface 116 may be establishedusing any suitable radio access technology (RAT).

More specifically, as noted above, the communications system 100 may bea multiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. Forexample, the base station 114 a in the RAN 104 and the WTRUs 102 a, 102b, 102 c may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA), whichmay establish the air interface 116 using wideband CDMA (WCDMA). WCDMAmay include communication protocols such as High-Speed Packet Access(HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink(DL) Packet Access (HSDPA) and/or High-Speed Uplink (UL) Packet Access(HSUPA).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement a radio technology such as Evolved UMTS TerrestrialRadio Access (E-UTRA), which may establish the air interface 116 usingLong Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/orLTE-Advanced Pro (LTE-A Pro).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement a radio technology such as NR Radio Access , which mayestablish the air interface 116 using NR.

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement multiple radio access technologies. For example, thebase station 114 a and the WTRUs 102 a, 102 b, 102 c may implement LTEradio access and NR radio access together, for instance using dualconnectivity (DC) principles. Thus, the air interface utilized by WTRUs102 a, 102 b, 102 c may be characterized by multiple types of radioaccess technologies and/or transmissions sent to/from multiple types ofbase stations (e.g., an eNB and a gNB).

In other embodiments, the base station 114 a and the WTRUs 102 a, 102 b,102 c may implement radio technologies such as IEEE 802.11 (i.e.,Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperabilityfor Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×, CDMA2000 EV-DO,Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), InterimStandard 856 (IS-856), Global System for Mobile communications (GSM),Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and thelike.

The base station 114 b in FIG. 1A may be a wireless router, Home Node B,Home eNode B, or access point, for example, and may utilize any suitableRAT for facilitating wireless connectivity in a localized area, such asa place of business, a home, a vehicle, a campus, an industrialfacility, an air corridor (e.g., for use by drones), a roadway, and thelike. In one embodiment, the base station 114 b and the WTRUs 102 c, 102d may implement a radio technology such as IEEE 802.11 to establish awireless local area network (WLAN). In an embodiment, the base station114 b and the WTRUs 102 c, 102 d may implement a radio technology suchas IEEE 802.15 to establish a wireless personal area network (WPAN). Inyet another embodiment, the base station 114 b and the WTRUs 102 c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE,LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. Asshown in FIG. 1A, the base station 114 b may have a direct connection tothe Internet 110. Thus, the base station 114 b may not be required toaccess the Internet 110 via the CN 106.

The RAN 104 may be in communication with the CN 106, which may be anytype of network configured to provide voice, data, applications, and/orvoice over internet protocol (VoIP) services to one or more of the WTRUs102 a, 102 b, 102 c, 102 d. The data may have varying quality of service(QoS) requirements, such as differing throughput requirements, latencyrequirements, error tolerance requirements, reliability requirements,data throughput requirements, mobility requirements, and the like. TheCN 106 may provide call control, billing services, mobile location-basedservices, pre-paid calling, Internet connectivity, video distribution,etc., and/or perform high-level security functions, such as userauthentication. Although not shown in FIG. 1A, it will be appreciatedthat the RAN 104 and/or the CN 106 may be in direct or indirectcommunication with other RANs that employ the same RAT as the RAN 104 ora different RAT. For example, in addition to being connected to the RAN104, which may be utilizing a NR radio technology, the CN 106 may alsobe in communication with another RAN (not shown) employing a GSM, UMTS,CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

The CN 106 may also serve as a gateway for the WTRUs 102 a, 102 b, 102c, 102 d to access the PSTN 108, the Internet 110, and/or the othernetworks 112. The PSTN 108 may include circuit-switched telephonenetworks that provide plain old telephone service (POTS). The Internet110 may include a global system of interconnected computer networks anddevices that use common communication protocols, such as thetransmission control protocol (TCP), user datagram protocol (UDP) and/orthe internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks 112 may include wired and/or wireless communications networksowned and/or operated by other service providers. For example, thenetworks 112 may include another CN connected to one or more RANs, whichmay employ the same RAT as the RAN 104 or a different RAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d in thecommunications system 100 may include multi-mode capabilities (e.g., theWTRUs 102 a, 102 b, 102 c, 102 d may include multiple transceivers forcommunicating with different wireless networks over different wirelesslinks). For example, the WTRU 102 c shown in FIG. 1A may be configuredto communicate with the base station 114 a, which may employ acellular-based radio technology, and with the base station 114 b, whichmay employ an IEEE 802 radio technology.

FIG. 1B is a system diagram illustrating an example WTRU 102. As shownin FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120,a transmit/receive element 122, a speaker/microphone 124, a keypad 126,a display/touchpad 128, non-removable memory 130, removable memory 132,a power source 134, a global positioning system (GPS) chipset 136,and/or other peripherals 138, among others. It will be appreciated thatthe WTRU 102 may include any sub-combination of the foregoing elementswhile remaining consistent with an embodiment.

The processor 118 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), anyother type of integrated circuit (IC), a state machine, and the like.The processor 118 may perform signal coding, data processing, powercontrol, input/output processing, and/or any other functionality thatenables the WTRU 102 to operate in a wireless environment. The processor118 may be coupled to the transceiver 120, which may be coupled to thetransmit/receive element 122. While FIG. 1B depicts the processor 118and the transceiver 120 as separate components, it will be appreciatedthat the processor 118 and the transceiver 120 may be integratedtogether in an electronic package or chip.

The transmit/receive element 122 may be configured to transmit signalsto, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, thetransmit/receive element 122 may be an antenna configured to transmitand/or receive RF signals. In an embodiment, the transmit/receiveelement 122 may be an emitter/detector configured to transmit and/orreceive IR, UV, or visible light signals, for example. In yet anotherembodiment, the transmit/receive element 122 may be configured totransmit and/or receive both RF and light signals. It will beappreciated that the transmit/receive element 122 may be configured totransmit and/or receive any combination of wireless signals.

Although the transmit/receive element 122 is depicted in FIG. 1B as asingle element, the WTRU 102 may include any number of transmit/receiveelements 122. More specifically, the WTRU 102 may employ MIMOtechnology. Thus, in one embodiment, the WTRU 102 may include two ormore transmit/receive elements 122 (e.g., multiple antennas) fortransmitting and receiving wireless signals over the air interface 116.

The transceiver 120 may be configured to modulate the signals that areto be transmitted by the transmit/receive element 122 and to demodulatethe signals that are received by the transmit/receive element 122. Asnoted above, the WTRU 102 may have multi-mode capabilities. Thus, thetransceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as NR and IEEE 802.11, forexample.

The processor 118 of the WTRU 102 may be coupled to, and may receiveuser input data from, the speaker/microphone 124, the keypad 126, and/orthe display/touchpad 128 (e.g., a liquid crystal display (LCD) displayunit or organic light-emitting diode (OLED) display unit). The processor118 may also output user data to the speaker/microphone 124, the keypad126, and/or the display/touchpad 128. In addition, the processor 118 mayaccess information from, and store data in, any type of suitable memory,such as the non-removable memory 130 and/or the removable memory 132.The non-removable memory 130 may include random-access memory (RAM),read-only memory (ROM), a hard disk, or any other type of memory storagedevice. The removable memory 132 may include a subscriber identitymodule (SIM) card, a memory stick, a secure digital (SD) memory card,and the like. In other embodiments, the processor 118 may accessinformation from, and store data in, memory that is not physicallylocated on the WTRU 102, such as on a server or a home computer (notshown).

The processor 118 may receive power from the power source 134, and maybe configured to distribute and/or control the power to the othercomponents in the WTRU 102. The power source 134 may be any suitabledevice for powering the WTRU 102. For example, the power source 134 mayinclude one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to the GPS chipset 136, which maybe configured to provide location information (e.g., longitude andlatitude) regarding the current location of the WTRU 102. In additionto, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 116 from abase station (e.g., base stations 114 a, 114 b) and/or determine itslocation based on the timing of the signals being received from two ormore nearby base stations. It will be appreciated that the WTRU 102 mayacquire location information by way of any suitablelocation-determination method while remaining consistent with anembodiment.

The processor 118 may further be coupled to other peripherals 138, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 138 may include anaccelerometer, an e-compass, a satellite transceiver, a digital camera(for photographs and/or video), a universal serial bus (USB) port, avibration device, a television transceiver, a hands free headset, aBluetooth® module, a frequency modulated (FM) radio unit, a digitalmusic player, a media player, a video game player module, an Internetbrowser, a Virtual Reality and/or Augmented Reality (VR/AR) device, anactivity tracker, and the like. The peripherals 138 may include one ormore sensors. The sensors may be one or more of a gyroscope, anaccelerometer, a hall effect sensor, a magnetometer, an orientationsensor, a proximity sensor, a temperature sensor, a time sensor; ageolocation sensor, an altimeter, a light sensor, a touch sensor, amagnetometer, a barometer, a gesture sensor, a biometric sensor, ahumidity sensor and the like.

The WTRU 102 may include a full duplex radio for which transmission andreception of some or all of the signals (e.g., associated withparticular subframes for both the UL (e.g., for transmission) and DL(e.g., for reception) may be concurrent and/or simultaneous. The fullduplex radio may include an interference management unit to reduce andor substantially eliminate self-interference via either hardware (e.g.,a choke) or signal processing via a processor (e.g., a separateprocessor (not shown) or via processor 118). In an embodiment, the WTRU102 may include a half-duplex radio for which transmission and receptionof some or all of the signals (e.g., associated with particularsubframes for either the UL (e.g., for transmission) or the DL (e.g.,for reception)).

FIG. 10 is a system diagram illustrating the RAN 104 and the CN 106according to an embodiment. As noted above, the RAN 104 may employ anE-UTRA radio technology to communicate with the WTRUs 102 a, 102 b, 102c over the air interface 116. The RAN 104 may also be in communicationwith the CN 106.

The RAN 104 may include eNode-Bs 160 a, 160 b, 160 c, though it will beappreciated that the RAN 104 may include any number of eNode-Bs whileremaining consistent with an embodiment. The eNode-Bs 160 a, 160 b, 160c may each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the eNode-Bs 160 a, 160 b, 160 c may implement MIMO technology. Thus,the eNode-B 160 a, for example, may use multiple antennas to transmitwireless signals to, and/or receive wireless signals from, the WTRU 102a.

Each of the eNode-Bs 160 a, 160 b, 160 c may be associated with aparticular cell (not shown) and may be configured to handle radioresource management decisions, handover decisions, scheduling of usersin the UL and/or DL, and the like. As shown in FIG. 10, the eNode-Bs 160a, 160 b, 160 c may communicate with one another over an X2 interface.

The CN 106 shown in FIG. 10 may include a mobility management entity(MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN)gateway (PGW) 166. While the foregoing elements are depicted as part ofthe CN 106, it will be appreciated that any of these elements may beowned and/or operated by an entity other than the CN operator.

The MME 162 may be connected to each of the eNode-Bs 162 a, 162 b, 162 cin the RAN 104 via an S1 interface and may serve as a control node. Forexample, the MME 162 may be responsible for authenticating users of theWTRUs 102 a, 102 b, 102 c, bearer activation/deactivation, selecting aparticular serving gateway during an initial attach of the WTRUs 102 a,102 b, 102 c, and the like. The MME 162 may provide a control planefunction for switching between the RAN 104 and other RANs (not shown)that employ other radio technologies, such as GSM and/or WCDMA.

The SGW 164 may be connected to each of the eNode Bs 160 a, 160 b, 160 cin the RAN 104 via the S1 interface. The SGW 164 may generally route andforward user data packets to/from the WTRUs 102 a, 102 b, 102 c. The SGW164 may perform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when DL data is available forthe WTRUs 102 a, 102 b, 102 c, managing and storing contexts of theWTRUs 102 a, 102 b, 102 c, and the like.

The SGW 164 may be connected to the PGW 166, which may provide the WTRUs102 a, 102 b, 102 c with access to packet-switched networks, such as theInternet 110, to facilitate communications between the WTRUs 102 a, 102b, 102 c and IP-enabled devices.

The CN 106 may facilitate communications with other networks. Forexample, the CN 106 may provide the WTRUs 102 a, 102 b, 102 c withaccess to circuit-switched networks, such as the PSTN 108, to facilitatecommunications between the WTRUs 102 a, 102 b, 102 c and traditionalland-line communications devices. For example, the CN 106 may include,or may communicate with, an IP gateway (e.g., an IP multimedia subsystem(IMS) server) that serves as an interface between the CN 106 and thePSTN 108. In addition, the CN 106 may provide the WTRUs 102 a, 102 b,102 c with access to the other networks 112, which may include otherwired and/or wireless networks that are owned and/or operated by otherservice providers.

Although the WTRU is described in FIGS. 1A-1D as a wireless terminal, itis contemplated that in certain representative embodiments that such aterminal may use (e.g., temporarily or permanently) wired communicationinterfaces with the communication network.

In representative embodiments, the other network 112 may be a WLAN.

A WLAN in Infrastructure Basic Service Set (BSS) mode may have an AccessPoint (AP) for the BSS and one or more stations (STAs) associated withthe AP. The AP may have access or an interface to a Distribution System(DS) or another type of wired/wireless network that carries traffic into and/or out of the BSS. Traffic to STAs that originates from outsidethe BSS may arrive through the AP and may be delivered to the STAs.Traffic originating from STAs to destinations outside the BSS may besent to the AP to be delivered to respective destinations. Trafficbetween STAs within the BSS may be sent through the AP, for example,where the source STA may send traffic to the AP and the AP may deliverthe traffic to the destination STA. The traffic between STAs within aBSS may be considered and/or referred to as peer-to-peer traffic. Thepeer-to-peer traffic may be sent between (e.g., directly between) thesource and destination STAs with a direct link setup (DLS). In certainrepresentative embodiments, the DLS may use an 802.11e DLS or an 802.11ztunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may nothave an AP, and the STAs (e.g., all of the STAs) within or using theIBSS may communicate directly with each other. The IBSS mode ofcommunication may sometimes be referred to herein as an “ad-hoc” mode ofcommunication.

When using the 802.11ac infrastructure mode of operation or a similarmode of operations, the AP may transmit a beacon on a fixed channel,such as a primary channel. The primary channel may be a fixed width(e.g., 20 MHz wide bandwidth) or a dynamically set width. The primarychannel may be the operating channel of the BSS and may be used by theSTAs to establish a connection with the AP. In certain representativeembodiments, Carrier Sense Multiple Access with Collision Avoidance(CSMA/CA) may be implemented, for example in 802.11 systems. ForCSMA/CA, the STAs (e.g., every STA), including the AP, may sense theprimary channel. If the primary channel is sensed/detected and/ordetermined to be busy by a particular STA, the particular STA may backoff. One STA (e.g., only one station) may transmit at any given time ina given BSS.

High Throughput (HT) STAs may use a 40 MHz wide channel forcommunication, for example, via a combination of the primary 20 MHzchannel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHzwide channel.

Very High Throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz,and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may beformed by combining contiguous 20 MHz channels. A 160 MHz channel may beformed by combining 8 contiguous 20 MHz channels, or by combining twonon-contiguous 80 MHz channels, which may be referred to as an 80+80configuration. For the 80+80 configuration, the data, after channelencoding, may be passed through a segment parser that may divide thedata into two streams. Inverse Fast Fourier Transform (IFFT) processing,and time domain processing, may be done on each stream separately. Thestreams may be mapped on to the two 80 MHz channels, and the data may betransmitted by a transmitting STA. At the receiver of the receiving STA,the above described operation for the 80+80 configuration may bereversed, and the combined data may be sent to the Medium Access Control(MAC).

Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. Thechannel operating bandwidths, and carriers, are reduced in 802.11af and802.11ah relative to those used in 802.11n, and 802.11ac. 802.11afsupports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space(TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and16 MHz bandwidths using non-TVWS spectrum. According to a representativeembodiment, 802.11ah may support Meter Type Control/Machine-TypeCommunications (MTC), such as MTC devices in a macro coverage area. MTCdevices may have certain capabilities, for example, limited capabilitiesincluding support for (e.g., only support for) certain and/or limitedbandwidths. The MTC devices may include a battery with a battery lifeabove a threshold (e.g., to maintain a very long battery life).

WLAN systems, which may support multiple channels, and channelbandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include achannel which may be designated as the primary channel. The primarychannel may have a bandwidth equal to the largest common operatingbandwidth supported by all STAs in the BSS. The bandwidth of the primarychannel may be set and/or limited by a STA, from among all STAs inoperating in a BSS, which supports the smallest bandwidth operatingmode. In the example of 802.11ah, the primary channel may be 1 MHz widefor STAs (e.g., MTC type devices) that support (e.g., only support) a 1MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.Carrier sensing and/or Network Allocation Vector (NAV) settings maydepend on the status of the primary channel. If the primary channel isbusy, for example, due to a STA (which supports only a 1 MHz operatingmode) transmitting to the AP, all available frequency bands may beconsidered busy even though a majority of the available frequency bandsremains idle.

In the United States, the available frequency bands, which may be usedby 802.11ah, are from 902 MHz to 928 MHz. In Korea, the availablefrequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the availablefrequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidthavailable for 802.11ah is 6 MHz to 26 MHz depending on the country code.

FIG. 1D is a system diagram illustrating the RAN 104 and the CN 106according to an embodiment. As noted above, the RAN 104 may employ an NRradio technology to communicate with the WTRUs 102 a, 102 b, 102 c overthe air interface 116. The RAN 104 may also be in communication with theCN 106.

The RAN 104 may include gNBs 180 a, 180 b, 180 c, though it will beappreciated that the RAN 104 may include any number of gNBs whileremaining consistent with an embodiment. The gNBs 180 a, 180 b, 180 cmay each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the gNBs 180 a, 180 b, 180 c may implement MIMO technology. For example,gNBs 180 a, 108 b may utilize beamforming to transmit signals to and/orreceive signals from the gNBs 180 a, 180 b, 180 c. Thus, the gNB 180 a,for example, may use multiple antennas to transmit wireless signals to,and/or receive wireless signals from, the WTRU 102 a. In an embodiment,the gNBs 180 a, 180 b, 180 c may implement carrier aggregationtechnology. For example, the gNB 180 a may transmit multiple componentcarriers to the WTRU 102 a (not shown). A subset of these componentcarriers may be on unlicensed spectrum while the remaining componentcarriers may be on licensed spectrum. In an embodiment, the gNBs 180 a,180 b, 180 c may implement Coordinated Multi-Point (CoMP) technology.For example, WTRU 102 a may receive coordinated transmissions from gNB180 a and gNB 180 b (and/or gNB 180 c).

The WTRUs 102 a, 102 b, 102 c may communicate with gNBs 180 a, 180 b,180 c using transmissions associated with a scalable numerology. Forexample, the OFDM symbol spacing and/or OFDM subcarrier spacing may varyfor different transmissions, different cells, and/or different portionsof the wireless transmission spectrum. The WTRUs 102 a, 102 b, 102 c maycommunicate with gNBs 180 a, 180 b, 180 c using subframe or transmissiontime intervals (TTIs) of various or scalable lengths (e.g., containing avarying number of OFDM symbols and/or lasting varying lengths ofabsolute time).

The gNBs 180 a, 180 b, 180 c may be configured to communicate with theWTRUs 102 a, 102 b, 102 c in a standalone configuration and/or anon-standalone configuration. In the standalone configuration, WTRUs 102a, 102 b, 102 c may communicate with gNBs 180 a, 180 b, 180 c withoutalso accessing other RANs (e.g., such as eNode-Bs 160 a, 160 b, 160 c).In the standalone configuration, WTRUs 102 a, 102 b, 102 c may utilizeone or more of gNBs 180 a, 180 b, 180 c as a mobility anchor point. Inthe standalone configuration, WTRUs 102 a, 102 b, 102 c may communicatewith gNBs 180 a, 180 b, 180 c using signals in an unlicensed band. In anon-standalone configuration WTRUs 102 a, 102 b, 102 c may communicatewith/connect to gNBs 180 a, 180 b, 180 c while also communicatingwith/connecting to another RAN such as eNode-Bs 160 a, 160 b, 160 c. Forexample, WTRUs 102 a, 102 b, 102 c may implement DC principles tocommunicate with one or more gNBs 180 a, 180 b, 180 c and one or moreeNode-Bs 160 a, 160 b, 160 c substantially simultaneously. In thenon-standalone configuration, eNode-Bs 160 a, 160 b, 160 c may serve asa mobility anchor for WTRUs 102 a, 102 b, 102 c and gNBs 180 a, 180 b,180 c may provide additional coverage and/or throughput for servicingWTRUs 102 a, 102 b, 102 c.

Each of the gNBs 180 a, 180 b, 180 c may be associated with a particularcell (not shown) and may be configured to handle radio resourcemanagement decisions, handover decisions, scheduling of users in the ULand/or DL, support of network slicing, DC, interworking between NR andE-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184 b, routing of control plane information towards Access andMobility Management Function (AMF) 182 a, 182 b and the like. As shownin FIG. 1D, the gNBs 180 a, 180 b, 180 c may communicate with oneanother over an Xn interface.

The CN 106 shown in FIG. 1D may include at least one AMF 182 a, 182 b,at least one UPF 184 a, 184 b, at least one Session Management Function(SMF) 183 a, 183 b, and possibly a Data Network (DN) 185 a, 185 b. Whilethe foregoing elements are depicted as part of the CN 106, it will beappreciated that any of these elements may be owned and/or operated byan entity other than the CN operator.

The AMF 182 a, 182 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 104 via an N2 interface and may serve as acontrol node. For example, the AMF 182 a, 182 b may be responsible forauthenticating users of the WTRUs 102 a, 102 b, 102 c, support fornetwork slicing (e.g., handling of different protocol data unit (PDU)sessions with different requirements), selecting a particular SMF 183 a,183 b, management of the registration area, termination of non-accessstratum (NAS) signaling, mobility management, and the like. Networkslicing may be used by the AMF 182 a, 182 b in order to customize CNsupport for WTRUs 102 a, 102 b, 102 c based on the types of servicesbeing utilized WTRUs 102 a, 102 b, 102 c. For example, different networkslices may be established for different use cases such as servicesrelying on ultra-reliable low latency (URLLC) access, services relyingon enhanced massive mobile broadband (eMBB) access, services for MTCaccess, and the like. The AMF 182 a, 182 b may provide a control planefunction for switching between the RAN 104 and other RANs (not shown)that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro,and/or non-3GPP access technologies such as WiFi.

The SMF 183 a, 183 b may be connected to an AMF 182 a, 182 b in the CN106 via an N11 interface. The SMF 183 a, 183 b may also be connected toa UPF 184 a, 184 b in the CN 106 via an N4 interface. The SMF 183 a, 183b may select and control the UPF 184 a, 184 b and configure the routingof traffic through the UPF 184 a, 184 b. The SMF 183 a, 183 b mayperform other functions, such as managing and allocating UE IP address,managing PDU sessions, controlling policy enforcement and QoS, providingDL data notifications, and the like. A PDU session type may be IP-based,non-IP based, Ethernet-based, and the like.

The UPF 184 a, 184 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 104 via an N3 interface, which may provide theWTRUs 102 a, 102 b, 102 c with access to packet-switched networks, suchas the Internet 110, to facilitate communications between the WTRUs 102a, 102 b, 102 c and IP-enabled devices. The UPF 184, 184 b may performother functions, such as routing and forwarding packets, enforcing userplane policies, supporting multi-homed PDU sessions, handling user planeQoS, buffering DL packets, providing mobility anchoring, and the like.

The CN 106 may facilitate communications with other networks. Forexample, the CN 106 may include, or may communicate with, an IP gateway(e.g., an IP multimedia subsystem (IMS) server) that serves as aninterface between the CN 106 and the PSTN 108. In addition, the CN 106may provide the WTRUs 102 a, 102 b, 102 c with access to the othernetworks 112, which may include other wired and/or wireless networksthat are owned and/or operated by other service providers. In oneembodiment, the WTRUs 102 a, 102 b, 102 c may be connected to a local DN185 a, 185 b through the UPF 184 a, 184 b via the N3 interface to theUPF 184 a, 184 b and an N6 interface between the UPF 184 a, 184 b andthe DN 185 a, 185 b.

In view of FIGS. 1A-1D, and the corresponding description of FIGS.1A-1D, one or more, or all, of the functions described herein withregard to one or more of: WTRU 102 a-d, Base Station 114 a-b, eNode-B160 a-c, MME 162, SGW 164, PGW 166, gNB 180 a-c, AMF 182 a-b, UPF 184a-b, SMF 183 a-b, DN 185 a-b, and/or any other device(s) describedherein, may be performed by one or more emulation devices (not shown).The emulation devices may be one or more devices configured to emulateone or more, or all, of the functions described herein. For example, theemulation devices may be used to test other devices and/or to simulatenetwork and/or WTRU functions.

The emulation devices may be designed to implement one or more tests ofother devices in a lab environment and/or in an operator networkenvironment. For example, the one or more emulation devices may performthe one or more, or all, functions while being fully or partiallyimplemented and/or deployed as part of a wired and/or wirelesscommunication network in order to test other devices within thecommunication network. The one or more emulation devices may perform theone or more, or all, functions while being temporarilyimplemented/deployed as part of a wired and/or wireless communicationnetwork. The emulation device may be directly coupled to another devicefor purposes of testing and/or performing testing using over-the-airwireless communications.

The one or more emulation devices may perform the one or more, includingall, functions while not being implemented/deployed as part of a wiredand/or wireless communication network. For example, the emulationdevices may be utilized in a testing scenario in a testing laboratoryand/or a non-deployed (e.g., testing) wired and/or wirelesscommunication network in order to implement testing of one or morecomponents. The one or more emulation devices may be test equipment.Direct RF coupling and/or wireless communications via RF circuitry(e.g., which may include one or more antennas) may be used by theemulation devices to transmit and/or receive data.

As described above, vehicular (“V2X”) communication is a mode ofcommunication in which WTRUs may communicate with each other directly.V2X communication is supported in Release 14 Long Term Evolution (“LTE”)communications, and was inspired from previous work on Device-to-Device(D2D) communications. V2X communication services may include one or moreof the following types. Vehicle to vehicle (“V2V”) communication mayallow vehicular WTRUs to communicate with each other directly. Vehicleto infrastructure (“V2I”) communication may allow vehicular WTRUs tocommunicate with roadside units (RSUs) and/or gNBs. Vehicle to network(“V2N”) communication may allow vehicular WTRUs to communicate with acore network. Vehicle to pedestrian (“V2P”) communication may allowvehicular WTRUs to communicate with other types of WTRUs, such as thosewith special conditions such as low battery capacity.

LTE defines two modes of operation for V2X communication. In Mode 3, thenetwork may give the WTRU a scheduling assignment for V2X sidelinktransmission. In Mode 4, the WTRU may autonomously select resources froma configured/pre-configured resource pool. Furthermore, LTE defines twocategories of resource pools for V2X communication, receiving pools andtransmitting pools. The receiving pools are monitored for receiving V2Xtransmissions. The transmitting pools are used by WTRUs to select thetransmission resources in Mode 4. Transmitting pools are not used byWTRUs configured in Mode 3.

The resource pools may be semi-statically signaled to WTRUs via RRCsignaling. In Mode 4, the WTRU may use sensing before selecting aresource from the RRC configured transmitting pool. LTE V2X may notsupport dynamic resource pools reconfiguration. Pool configuration mayonly be carried via a system information block (SIB) and/or dedicatedRRC signaling.

The next generation of wireless systems, referred to as New Radio (“NR”)systems, are currently being developed. NR systems are expected tosupport a number of use cases such as enhanced mobile broadband(“eMBB”), ultra-high reliability and low latency communications(“URLLC”), and enhanced V2X communication. V2X communication in NR isexpected to support new services for both safety and non-safetyscenarios (e.g., sensor sharing, automated driving, vehicle platooning,and remote driving).

Vehicle Platooning may enable vehicles to dynamically form a group whiletravelling together. Vehicles in the platoon may receive periodic datafrom a lead vehicle in order to carry on platoon operations. Thisinformation may allow the distance between vehicles to become extremelysmall. For example, the gap distance translated to time may be very low(e.g. sub second). Platooning applications may allow the vehiclesfollowing the lead vehicle to be autonomously driven.

Advanced driving may enable semi-automated or fully-automated driving.Longer inter-vehicle distance may be assumed. A vehicle and/or RSU mayshare data obtained from its local sensors with vehicles in proximity.This may allow vehicles to coordinate their trajectories or maneuvers.In addition, a vehicle may share its driving intention with vehicles inproximity. This may allow safer traveling, collision avoidance, andimproved traffic efficiency.

Extended sensors may enable the exchange of raw or processed datagathered through one or more of local sensors or live video data amongvehicles, RSUs, pedestrian devices, and V2X application servers. Thevehicles may enhance the perception of their environment beyond whattheir own sensors can detect and may have a more holistic view of thelocal situation.

Remote driving may enable a remote driver or a V2X application tooperate a remote vehicle for passengers who cannot drive themselves or aremote vehicle located in dangerous environments. For a case wherevariation is limited and routes are predictable, such as publictransportation, driving based on cloud computing may be used. Inaddition, access to cloud-based back-end service platform may be used.It should be noted that different V2X services may require differentperformance requirements, and for some scenarios, 3 ms latency may berequired.

In vehicle platooning, certain messages may need to be transmitted tothe entire platoon of vehicles and other messages may need to betransmitted to only one vehicle in particular. Many messages may betransmitted between WTRUs in the same platoon (for example, usingunicast transmission). It may be inefficient to allocating allocated aunique L2 identification (ID) for each combination of WTRUs that cancommunicate with each other as is done in conventional D2Dcommunication.

Transmission resources used by vehicles within a platoon may havedeterministic timing relationship. This timing relationship may berequired to address certain requirements for vehicle platooning. Forexample, the very short latency between transmissions of successiveWTRUs in a platoon require resources available for each WTRU to have ashort timing offset. Methods to ensure resource coordination andmanagement may be required at the access spectrum (AS) layer sinceindependent resource reservations by each WTRU may not be feasibleand/or may be inefficient.

In addition, SA1 requirements indicate that the AS may need to controlthe communication range for a message based on message characteristics.Methods may be required for the WTRU to distinguish the requiredtransmission range based on characteristics of the message and be ableto use sidelink transmission resources efficiently.

The platoon is a V2X application layer concept that manifests itself atthe access stratum as a group of WTRUs. The WTRUs may be related to oneanother in terms of geographical location, resource usage, sensing,and/or addressing. The description herein may include the general notionof a WTRU group, which could be formed from a platooning application orfrom other V2X applications. The WTRU group in this context may have oneor more of the following characteristics. WTRUs may move together orhave related geolocation and/or topology. WTRUs may need to communicatein multicast with an entire group. WTRUs may need to communicate inunicast to specific members of the group.

In one example, group members may be determined through applicationlayer management/signaling. Group formation and modification decisionsmay be made by an associated V2X application (e.g., a platoonapplication). Group information may be made fully available to the AS.For instance, a list of WTRUs that are part of the group may becommunicated periodically to the AS.

In another example, group determination and/or modification may bedetermined by the application layer and known only to the applicationlayer. The AS layer may receive specific information that ensures WTRUbehavior, relative to addressing and resource usage, reflects thepresence and topology of the group. The application layer may indicatethat a WTRU should take on specific AS behavior when that WTRU has beenmade the group leader at the application layer.

A WTRU may receive the following information from the application layer.With each application layer packet, the WTRU may receive one or more ofan indication of whether the packet should be transmitted in multicastor unicast, range information, timing requirements, and an indication ofwhether a packet needs to be relayed throughout the group. Periodically,or upon specific triggers from the application layer, the WTRU mayreceive one or more of an indication that the WTRU is part of or nolonger part of a group of WTRUs at the AS and the associated group ID,and indication that the WTRU should start or stop performing certaingroup lead AS behavior, and indication of the addition/or removal ofanother WTRU from a group and its associated ID, a WTRU's member ID, andproximity information of different WTRUs in a group (e.g., orientation,distance, etc.).

A WTRU may further apply certain behavior associated only with datapackets, services, and/or control information associated with groupcommunication. More specifically, the information above may beassociated with only a set of services, possibly identified by a serviceID, destination ID, or other identifier provided by the applicationlayer.

Conventional methods of V2X communication may not have procedures forunicast addressing. Some types of D2D communication allow for unicastand multicast addressing. For unicast addressing in D2D, a WTRU's ProSeWTRU ID may be used as the L2 Destination ID in place of the ProSe L2Group ID. While this may enable transmission of unicast messages withina group, this approach may have the following issues. The applicationlayer may need to reserve unique identifiers for services which aredifferent than any WTRU's ProSe WTRU ID. In addition, given a possiblelarge address space, the entire address may need to be included in theheader of any packet transmitted by the MAC layer. Also, groupidentification in D2D and conventional V2X may only refer to a service,without specifically implying any physical relationship between thedestination WTRUs. As a result, the AS may not know whether atransmission is related to a service (e.g., a conventional concept ofgrouping) or a physical grouping of WTRUs to enable platooning.

It should be noted that the term “group communication” may refer tocommunication within a group of physically related WTRUs (e.g., aplatoon) and not in the context of conventional group communication.Without loss of generality, a group communication may refer tocommunication between two WTRUs (unicast) or multiple WTRUs (multicast).A group destination address may be used as the destination address forunicast or multicast communication.

A WTRU may be provided with and use (e.g., in the MAC header) adifferent destination address structure depending on one or more of thefollowing: whether or not an application layer packet is associated withcommunication for a specific group (e.g., physical grouping), whetherthe transmission is a unicast transmission within that physicalgrouping, and whether the transmission is multicast to the entire groupin the physical grouping. More specifically, a destination address mayhave the following structure: service ID+group ID+member ID. The groupID and member ID may be optional and used only in the case of groupcommunication. The WTRU may transmit a MAC header with a variable headersize based on the received destination address from the applicationlayer. The WTRU may further indicate a header type to distinguish eachof the transmission cases. The service ID may be omitted by the MAClayer in the case of group communication. The service ID may betransmitted within the application layer information.

A WTRU may perform different behaviors relative to multiplexing andresource selection depending on the destination address received fromthe application layer for transmission over sidelink. The WTRU may allowmultiplexing of AS group control information, such as resourcecoordination information (“RCI”), with packets having a destinationaddress that contains a group ID and no member ID. The WTRU may performgroup-based resource selection for a group of communicating WTRUs whenthe packets have a destination address that contains at least a groupID. The WTRU may rely on group-based resources reserved by another WTRUassociated with the same group when the packet has a destination addressthat contains at least a group ID. The WTRU may transmit a reservationsignal for group-based resources indicated in the group ID when thepacket has a destination address that contains at least a group ID.

Sidelink resources may be reserved for group communications. A SidelinkControl Information (“SCI”) may indicate that a transmission isassociated with a specific group (e.g., by inclusion of a groupidentifier in the SCI). In this case, a WTRU may include only a memberID in the MAC layer header for transmissions associated with thesededicated resources or transmission scheduled by the SCI. For atransmission that is broadcast to an entire group, the WTRU may includea special member ID (e.g., all 0s) to distinguish this as a multicasttransmission to the entire group. The WTRU may not include a member IDand may use the MAC header type to distinguish this as a multicasttransmission to the entire group.

A WTRU may receive a L2 destination address from upper layers to be usedfor group communication. The WTRU may receive the L2 source IDs of theWTRUs that form the group along with the L2 destination address.

A WTRU may receive a set of unique L2 destination addresses from upperlayers for use in group communication. A WTRU may select one of theseaddresses to be used for group communication that may be formed and/ormanaged by the WTRU. The WTRU may further inform the upper layers of theL2 source addresses of the WTRUs that form the group and thecorresponding L2 destination group address.

A WTRU may inform other WTRUs in a group of the destination address tobe used for group communication. A WTRU may initiate group formationsignaling between WTRUs (e.g., though RRC messages) whereby thedestination address for a group can be exchanged.

A WTRU may use a dedicated destination L2 address for exchanging groupformation and/or group maintenance signaling. For example, thedestination L2 address may indicate that the message is a control planemessage rather than a user plane message. A WTRU that receives a messagewith a dedicated control plane destination ID may route the message tothe RRC entity within the WTRU's protocol stack. A WTRU that transmitsan inter-WTRU control plane signaling message (e.g., an RRC message) mayutilize the dedicated destination L2 address for control messages. AWTRU may determine the dedicated L2 address for control plane signalingbased on preconfiguration. The WTRU may determine this address from theupper layers.

A WTRU that is part of a configured group may utilize a set of resourcesthat are reserved for communication by members of the same group ofWTRUs. This may allow for lower-latency and/or higher reliabilitycommunication between WTRUs in a group. Interference/contention withWTRUs outside of the group, which may be in proximity to the group, maybe avoided. Low latency and/or high reliability may be required forintra-group communication.

A WTRU may be configured with one or more resource pools used for groupcommunication. The WTRU may receive a configuration of one or moregroup-specific resource pools in a broadcast (SIB), in dedicatedsignaling, or in preconfiguration. The group-specific resource pool maybe determined from this configuration based on one or more of the WTRU'sgeographical location, WTRU speed, WTRU heading, group ID, member ID,and application layer information (e.g. related to topology).

A resource pool configuration may be associated with a group ID. A WTRUmay receive a packet from the upper layers that is intended fortransmission to a specific group (i.e., the destination address matchesthe destination address of the group). The WTRU may select resourcesfrom the group-specific pool for transmission. The WTRU may further useresources from the group-specific pool under certain conditionsassociated with the packet to be transmitted. The conditions may be oneor more of the following QoS-related conditions: the packet has certaindelay budget that meets a predetermined criteria, the packet needs to betransmitted in unicast or multicast fashion, the packet has a certainrequired range of transmission or specific directionality fortransmission (e.g., as determined by the application), the packet isassociated with a certain data rate requirement, and the packet has acertain priority.

A WTRU may be configured with group specific pool for reception, whichmay be derived in a similar manner. A WTRU may monitor resources fromthe group specific pool when any of the conditions above are satisfied.

A WTRU may receive a group-specific resource pool configuration in theRRC configuration. The group-specific resource pool configuration mayindicate the use of one or more resource pools depending on the WTRU'sgeolocation and the group ID. The WTRU may select a group-specificresource pool from the set of pools in the configuration based on itsgeolocation and group ID. The WTRU may select the resource pool using amodulo operation on its latitude/longitude and group ID. Morespecifically, the pool configuration may consist of a table of M×Nresource pools and the WTRU may determine the index of the resource poolin the table to use at any time by the following equations:

m=(lat/long)mod M   Equation 1

n=(group ID)mod N.   Equation 2

The WTRU may use the group-specific resource pool whenever the WTRU isassigned to a group and has transmissions for that group. Otherwise, theWTRU may use other TX pools. A WTRU may receive a message from theapplication layer that it has been assigned to a specific group. Themessage may contain an associated group identifier. Following suchassignment, the WTRU may choose resources from the group specific poolwhen it receives a packet from the upper layers for transmission. Thepacket may be tagged by the same group identifier. The WTRU may furtherselect resources from the group specific resource pool which depend on amember ID within the group.

A WTRU in a group may transmit a group reservation signal on thesidelink channel to reserve resources usable by a number of WTRUs thatare part of the group. The WTRU may be further configured to transmitthe reservation signal along with its own sidelink data transmissions.The reservation signal may be further transmitted along with sidelinkdata transmissions that are intended for the same group for which thereservation signal is being transmitted. For example, a WTRU maytransmit an SCI which serves as a reservation signal for resources thatcan be used by a group. The SCI may include the group identifier, or aportion of the group identifier. The WTRU may further schedule data onthe PSSCH that the WTRU is transmitting using the same SCI. The data mayhave one or more members of the group as intended destination.

The group reservation signal may be a field in an existing V2Xtransmission on PSCCH or PSSCH, a new message transmitted on either ofthese channels, or a combination of both. More specifically, thereservation signal may be transmitted in one or more of the followingways: a field in the sidelink scheduling assignment, SCI, or similarmessage on PSCCH; a synchronization signal, or field transmitted withina synchronization signal, similar to PSBCH; and a message (e.g., MAC CE,RRC, or application layer message) contained on the PSSCH. This messagemay further be transmitted within the resources which the groupreservation signal is intending to reserve.

The reservation signal may provide one or more of the following piecesof information. The reservation signal may provide a group indication orgroup identification to specify the particular group of WTRUs for whichthe resource is reserved. The reservation signal may provide anindication of the resources being reserved, such as the time, frequency,beam, or set of beams. This indication may be implicitly included in thescheduling information provided by the scheduling message. For example,the reservation signal may reserve the resources that the SCI isintending to schedule. In addition, this indication may further consistof additional information for the reservation which is not included inthe scheduling information. For example, the reservation signal mayindicate the reservation of the scheduled resources for a number ofsubframes, time periods, or it may indicate the subset of the scheduledresources. The reservation signal may provide resource coordinationinformation (RCI) for coordination of the resources between multipleWTRUs. The reservation signal may provide geolocation of the WTRUtransmitting the resource reservation signal.

RCI for a specific group or group-reserved resources may be transmittedin sidelink by one or a number of WTRUs (e.g. group leader), relayed bya WTRU, or transmitted by all WTRUs. A WTRU may further be configured byupper layers to transmit and/or relay RCI. RCI may be transmitted aspart of the resource reservation signal. RCI may be transmitted as anaccess stratum control message, such as a MAC CE or inter-WTRU controlmessage on sidelink. For example, a WTRU configured to transmit RCI maydo so periodically, or upon changes in content of RCI (e.g., a change ina set of WTRUs in a group). RCI may be provided to a WTRU by theapplication layer and changed upon the change of group topology (e.g., achange in the number of vehicles in a platoon or their sequencing).

A specific or designated WTRU may transmit RCI to indicate thesequencing for the usage of the resources reserved for a group in thegroup reservation signal. A WTRU may transmit RCI to indicate its usageor non-usage of a resource or subresource. For example, a WTRU mayindicate to the remainder of the group that it will not use thesubresources that were assigned to it by any method described herein.Another WTRU which may be indicated in the RCI or determined by specificrules (e.g., an WTRU with the next largest member ID) may use thesubresources of the WTRU that sent the indication.

A WTRU may transmit RCI to indicate sensing results it determines forresources associated with a group. For instance, a WTRU may transmit oneor more of the RSRP, RSSI, and occupancy information it detects (e.g.,SCI transmissions reserving resources which are not associated with itsown group) as part of the SCI.

RCI associated for a specific group may be read only by members of thatgroup. For example, a WTRU may transmit RCI as a MAC CE in a MAC SDUhaving a destination address that matches the group destination address.While the SCI may reserve the resources for a group and be visible toWTRUs outside the group, the RCI may indicate such resource usage withinthe group and may be visible only to WTRUs within the group.

RCI may indicate the allowed time/frequency/beam sequencing of a WTRU'sown transmission subresources within a set of subresources. This may bein the form of a table, bitmap, or ordering of member IDs. The size ofthe RCI may be decided, for example, by the application layer based onplatoon topology. The size of the table/bitmap may be communicated bythe application layer.

RCI may indicate conditions for use of a subresource associated with aWTRU's own transmissions or with transmissions of other WTRUs, such as:minimum priority of data for which a WTRU can utilize its ownsubresources in a group, and minimum priority of data for which a WTRUcan utilize other subresources in a group. These conditions may bepreconfigured in the WTRU and not be transmitted with the RCI.

The RCI may indicate rules and/or indications for changing thesequencing of subresource usage. For example, the RCI may contain anindication that a WTRU may use other un-used subresources belonging toother WTRUs. The RCI may indicate rules for whether/when a WTRU cantransmit a new RCI. The RCI may indicate a set of resources to be sensedby a specific WTRU in the group. For example, the RCI may contain anindication of which time/frequency/bwp/beam a given WTRU should performsensing on for monitoring of SCI, and possible reporting in relatedcontrol information. The RCI may indicate buffer occupancy information,such as the amount of data pending in the WTRU's buffer and potentiallyassociated with transmission for a specific group of WTRUs and/orassociated with different QoS requirements. The RCI may indicate arandom number associated with the selection by that WTRU of the numberof reservation periods that should be reserved. The RCI may indicatesensing results (e.g., RSRP, RSSI, and resource occupancy/availabilityinformation) obtained by a specific WTRU's sensing procedure.

A WTRU that receives a resource reservation signal for a group maytransmit coordination information (i.e., its own RCI) as part of its owntransmissions, or within the subresource reserved for it. Thecoordination information may serve other WTRUs that transmit theresource reservation signal for determining the resources to be reservedin a future reservation period, or in determining the RCI to betransmitted. The coordination information can be transmitted in acontrol message (e.g., a MAC CE, or sidelink RRC message) and may beappended to any data transmitted by a WTRU on its own subresources.

The coordination information may include the WTRU's own member ID orsimilar ID identifying the WTRU, which may be provided by theapplication layer. The coordination information may include sensingresults, such as an indication of the available/unavailable resources asdetermined by the WTRU. The sensing results may be further specific to asubset of overall resources (e.g., time, frequency, BWP, beam) that maybe indicated for that WTRU in the RCI. The coordination information mayinclude a number of reservation periods for which the WTRU intends tomaintain/keep use of its assigned subresources. The coordinationinformation may include QoS information of resources in the WTRU'sbuffers, such as priority, latency, periodicity, rate, rangerequirements, and payload. The coordination information may includeabsolute values of or change in value of timing, size, and periodicityof any periodical information received from upper layers, such asperiodic CAM traffic or similar periodic application layer traffic. Thecoordination information may include a difference or time offset betweena WTRU's assigned subresource and arrival of data to be transmitted inthe subresource. Potential changes to this time difference may beincluded. The coordination information may include buffer status of aWTRU.

A WTRU may receive RCI from a designated WTRU that indicates a set ofresources on which it should perform regular sensing for availabilitydetermination. When transmitting data in its subresources, possiblyindicated by the resource reservation signal it receives, a WTRU mayinclude the available/unavailable resources and the number ofreservation periods for which it intends to continue periodictransmission in its assigned subresources. This information may betransmitted in a MAC CE included with its own data transmissions.

A WTRU may be identified as the designated WTRU for transmission of aresource reservation signal. The WTRU may receive coordinationinformation from the other WTRUs in a group containing any of theinformation in the coordination information sent by the individual WTRU.A WTRU may use the received information to perform resource reservationin the next reservation period, and may indicate the reservedresources/subresources in its next transmission of the resourcereservation signal.

A WTRU may no longer require the resources booked for it within theresources for the group (e.g., the same resources over a number ofreservation periods) for a certain number of reservation periods. Inthis case, the WTRU may indicate its non-usage of its assignedsubresources for future reservation periods. As a result, the WTRUtransmitting the resource reservation signal may assign another WTRU inthe group to the same subresources by transmitting updated informationin the RCI.

A WTRU may transmit a reservation signal as a result of one or more ofthe following triggers. A WTRU may transmit a reservation signal uponthe initiation of a specific service from the application layer, such asa V2X service requiring intra-group communication. A WTRU may transmit areservation signal upon creation of a logical channel with a certainpriority, certain QoS characteristics, specific range requirements, orreservation for communication within a group of WTRUs. A WTRU maytransmit a reservation signal upon reception from the application layerof an indication from the application layer to transmit such areservation signal. A WTRU may transmit a reservation signal uponreception of data from the application layer, possibly associated with agroup. A WTRU may transmit a reservation signal based on expiry of atimer, possibly configured by application layer and/or RRC signalingand/or broadcast system information.

A WTRU may transmit a reservation signal upon reception by the PHY layerof a reservation signal transmitted by another WTRU. This trigger may befurther conditioned on one or more of the following criteria. If thereceived reservation signal contains a group ID which matches one of theactivated or configured group IDs at the WTRU, the WTRU may transmit thereservation signal. If the received reservation signal is received witha power below a threshold, the WTRU may transmit the reservation signal.If the received reservation signal indicates that the WTRU's position insequence is a specific position, the WTRU may transmit the reservationsignal. If a WTRU's member ID or position within a sequence oftransmission matches the next expected transmission, as determined bythe received reservation signal, the WTRU may transmit the reservationsignal. After a configured or indicated time following reception of thereservation signal, the WTRU may transmit the reservation signal. TheWTRU may transmit a reservation signal if the received reservationsignal is measured below a threshold. The WTRU may transmit areservation signal if the received reservation signal is received from aWTRU whose distance is above/below a threshold.

A WTRU may receive an indication from upper layers (e.g., a V2Xapplication layer, a V2X control layer, a ProSe layer, or NAS) to starttransmission of a reservation signal for a specific group associatedwith a group identifier. The WTRU may transmit a reservation signalperiodically following reception of such higher layer indication, untilreceiving an indication to disable/stop transmission of the reservationsignal.

A WTRU may receive an indication from the upper layers to starttransmission of a reservation signal for a specific group associatedwith a group identifier, and the WTRU may transmit the reservationsignal upon reception of data intended for that group of WTRUs receivedfrom the upper layers.

A WTRU may receive an indication from the upper layers that it is partof a specific communication group. The WTRU may transmit a reservationsignal when it detects a resource reservation signal transmitted byanother WTRU in a previous reservation period if the RCI indicates thatthe resource is still available in the next reservation period and theWTRU is next in the sequence to transmit on the reserved resource.

A WTRU may be configured or indicated, for example, by application layeror by reception of sidelink control messages from one or more otherWTRUs, to reserve resources to be used by a group of WTRUs. For example,one or more WTRUs of a group may be designated or allowed (e.g., asconfigured by the application layer) to reserve resources for usage byall WTRUs in the group. The WTRU may perform a resource selectionprocedure, which may consist of determining a set of available resourcesbased on sensing results. The WTRU may transmit a reservation signal toreserve the selected resources which are available based on sensingresults. The WTRU may further perform resource selection for multipleWTRUs, possibly associated with a group. The WTRU may determine theamount of resources to be selected, as well as the structure of theresources.

Resource structure may refer to a periodicity of resources. For example,resource selection may select a number of resources occurring with afixed periodicity. Resource structure may refer to a number ofsubresources. For example, a WTRU may select a fixed number ofsubresources for a single or multiple one-shot transmissions by eachWTRU.

Resource structure may refer to time spacing between subresources. Forexample, resource selection may select a number of subresourcesassociated with each resource. Each subresource may be usable by asingle WTRU in a group. The time difference (in slots) between suchsubresources may be fixed or may be such that they do not exceed aspecific maximum time difference.

Resource structure may refer to the size of each subresource.Subresources may be reserved so that each subresource is of the samesize, or may have some relation in size between each subresource. Thesize of each subresource may be provisioned to support the maximumpacket size of each WTRU transmission in the group reservation. The sizeof each subresource may be determined by the data rate requirements ofeach WTRU. The size of each subresource may be indicated by theapplication layer. The size of each subresource may be determined by thesize of the data required for transmission by the WTRU transmitting thereservation signal.

Resource structure may refer to a frequency range (e.g., BWP) over whichany portion or all of the resources should be reserved. For example,resource selection may reserve all resources only in a specific BWP, ora first number of subresources in a first BWP and a second number ofsubresources in a second BWP.

Resource structure may refer to a beam or set of beams over which anyportion, or all of the resources should be reserved. For example,resource selection may reserve resources only from a subset of beams,beam directions, or pools associated with beam directions.

A WTRU may transmit information related to the resource reservationstructure in its own transmission. The information may or may not beaccompanied by its own data transmission. For example, a WTRU maytransmit the information above in an SCI. The information may beidentified by indexing of certain fixed resource structures (e.g., asper a table).

During resource selection, a WTRU may determine the size and structureof the resources to be selected based on one or more of the followingcriteria. The determination may be based on the amount of data the WTRUitself needs to transmit (i.e., the size of data pending in WTRU'sbuffer). For example, the WTRU may reserve N subresources of size M. Thesize M may be determined based on the size of data the WTRU needs totransmit. The number N may be determined by the application layer data,for example, indicating the number of WTRUs currently in the group.

The determination may be based on the QoS characteristics of data totransmit (e.g., delay requirements, priority, data rate, reliability,and transmission range). The determination may be based on MCS asdetermined by the WTRU or by the gNB. The determination may be based onoccupancy measurements (e.g., CBR measurements) made by the WTRU orcommunicated to the WTRU by other WTRUs, possibly in the same group. Thedetermination may be based on beam-level quality measurements. Thedetermination may be based on group-specific information obtained fromthe application layer. For example, the number of subresources may beindicated by the application layer, or may be derived from an indicatednumber of WTRUs in the group. The spacing between different subresourcesmay be directly indicated by the application layer.

The determination may be based on an expectation of the size of thetransmission from the other WTRUs, potentially based on the size of thetransmission of the designated WTRU. For example, the designated WTRUmay transmit a request message, from which it expects a response frommultiple WTRUs. The size of the response message may be deterministic.

A WTRU may be configured to transmit a reservation signal along with itsown data transmission intended for a group. The WTRU may receive a setof parameters for group reservation from the higher layers whichconsists of a time interval between subresources, a number ofsubresources associated with a resource, a subband (e.g., BWP) for theresources, and a group identifier. Upon reception of data from upperlayers associated with the group or upon the initiation of a servicespecific to the group, the WTRU may perform resource reservationprocedure by which the WTRU does one or more of the following. The WTRUmay determine the amount of resources for one subresource based on thesize of its own transmissions. The WTRU may determine the subresourcepattern and/or the periodicity of the reserved resources. The WTRU maydetermine the number of subresources to reserve based on the applicationlayer information. The WTRU may select a set of subresources which matchthe required time interval and subband from the higher layers. The WTRUmay transmit a resource reservation signal (possibly with its own data)that indicates the presence of its own data as well as the reservationof other resources usable by other WTRUs.

A WTRU may perform a group resource reservation procedure in conjunctionwith other resource reservation/transmission that may not be associatedwith the group. For example, the procedure may be used only when thedata received by upper layers is associated with group identifierconfigured at the WTRU.

A WTRU may transmit a reservation signal along with its own datatransmission. The reservation signal may be a response message to itsown transmission. The WTRU may reserve enough resources for a singleresponse by each WTRU. The WTRU may autonomously reserve the timing ofthe resources for each of the WTRU responses such that one or more ofthe following criteria may be met. The WTRU may receive all responseswithin a specific time frame, whereby the time frame may be related tothe QoS of the request/response. or any data which depends on therequest response. The response messages may not overlap intime/frequency/beam. The response message of one WTRU in the group mayalso be received by another WTRU in the group.

A WTRU may be configured to monitor sidelink transmissions for aresource reservation signal and use resources reserved by another WTRUwhich were intended for group communication. Upon reception of aresource reservation signal indicating resources available fortransmission by a group (e.g., identified by a group identitytransmitted in SCI), the WTRU may transmit pending data intended for theassociated group identity in a portion of the reserved resources, suchas in a subresource of the resources identified in the resourcereservation signal. A WTRU may use the resources only for transmissionof data intended for the specific group for which the WTRU resourceswere reserved. If the WTRU does not have pending data intended for thegroup associated with the resource reservation signal, the WTRU mayignore the resources and not use them for transmission.

A WTRU may transmit non-group data in a subresource associated with agroup, but it may prioritize group data over non-group data. Morespecifically, the WTRU may utilize the entire subresource forgroup-based data as long as it has data associated with that group.Otherwise, it may use the resources to also transmit non-group-baseddata.

A WTRU may delay transmission of group-data until the occurrence of itsassociated resource within the group or subresource. The decision todelay transmission of group-data may be conditioned on the timeremaining until the occurrence of the group data (e.g., as determined bythe RCI) as well as the priority and/or latency requirements of thegroup data. For example, the WTRU may compare the required time fortransmission of the group data upon arrival of the packet to theexpected occurrence of the group subresource. The WTRU may decide todelay transmission until the occurrence of the subresource, as long asthe subresource occurs some time delta prior to the requiredtransmission time. The time delta may be zero. If a WTRU determines notto wait for the group subresource, it may perform resource selection andtransmission on a non-group resource.

A WTRU may be required to transmit data with a specific priority (e.g.,as determined by the PPPP) in the group resource. More specifically, thegroup resource may be associated to data having a specific priority. Thepriority associated with the group resource may be contained in thegroup reservation signal (e.g., in the SCI). A WTRU may be allowed totransmit only group data matching the priority transmitted in thereservation signal. The WTRU may also transmit data of any priority(e.g., less than or greater than the priority in the reservation signal)in the group resource.

A WTRU may change the priority associated with a group resource. Thechange may occur at the time in which the WTRU decides to performreselection for the group resource, as described herein.

In addition to the data associated with the group, the WTRU may alsotransmit RCI. The RCI may contain the buffer information associated withdata intended for the group. For example, the WTRU may transmit theamount of data in its buffers intended for the group, possibly withpriority/reliability or other QoS information. The WTRU may indicatewithin the RCI whether segmentation was required to transmit the data inthe allocated resource. The WTRU may also indicate the size of thepacket which required segmentation to fit in the group subresource.

If the WTRU does not have data to transmit associated with the group, itmay transmit RCI indicating it will not need the resource in the nextreservation period or transmit a buffer status indicating it has no datain its buffers associated with the resource.

A WTRU may indicate in RCI that it was not able to use the groupresource because the WTRU decided to use a transmission on a non-groupresource (e.g., due to the group resource not meeting the WTRU's latencyrequirements). The WTRU may also indicate the amount of time by whichthe group resource was not able to meet its latency requirements.

The WTRU may indicate in RCI that it detected SCI transmission byanother WTRU that schedules a non-group transmission that collides withthe its own group scheduled transmission.

The WTRU may indicate in RCI the presence of buffered group data with apriority which is different than the priority allowable for transmissionon the group resource.

A WTRU may make a resource reselection decision when the resourcereserved for the group is an SPS-like or forward-booked resourceintended for use by WTRUs of the group. Resource reselection may beperformed by any WTRU in the group or resource reselection may beperformed by only a single WTRU. For example, in a case where each WTRUtransmits the resource reservation signal, which may include SCI andRCI, to schedule its own transmissions, any WTRU may perform resourcereselection prior to its own scheduled transmission. In a case where asingle WTRU (e.g., a designated WTRU) transmits the SCI to schedule allof the group subresources, resource reselection may be performed by onlya single WTRU in the group.

A WTRU may perform resource reselection based on one or more of thefollowing triggers or conditions. Resource reselection may be performedby a WTRU prior to its own scheduled transmission on a resource orsubresource. For example, a WTRU may not be allowed to perform resourcereselection until the WTRU determines (e.g., by RCI and member ID) thatthe next resource is reserved for its own transmission.

Resource reselection may be performed if a resource does not meet theWTRU's own latency requirements. For example, a WTRU may determine thatthe expected timing of its next resource does not meet the latencyrequirements of a packet that arrives from the upper layers. The WTRUmay perform resource reselection in order to schedule its owntransmission at an earlier point in time as compared to the scheduledperiodic resource.

Resource reselection may be performed if a resource does not meet theWTRU's own buffer requirements. For example, the WTRU may determine thatthe allocated resource/subresource would require segmentation of thepacket at L2 and the WTRU may decide not to segment the packet.

Resource reselection may be performed if transmission of controlinformation (e.g., RCI) from other WTRUs indicates that the latencyand/or buffer requirements of other WTRUs are not met. For example, aWTRU may receive RCI from one or more other WTRU transmissions in thegroup. The WTRU may perform resource reselection if one or more of theWTRUs indicate one or more of a need to segment a packet to transmit itin the group resource, an inability to transmit group data within theallocated group resource due to the group resource not meeting latencyrequirements, and a detection of collision of subresources with anothernon-group transmission.

Resource reselection may be performed upon detection of a scheduledtransmission by another WTRU not belonging to the group or a non-grouptransmission that collides with a scheduled resource. This may beperformed potentially only if the non-group transmission is determinedto be higher priority than the group transmission.

Resource reselection may be performed if a different carrier, bandwidth,or beam becomes better than the current carrier, bandwidth, or beam by apredetermined or configured amount. For example, a WTRU may maintain CBRmeasurements of the current carrier, bandwidth, and beam in addition toother carriers, bandwidths, and beams and may decide to reselect whenthe CBR of another carrier, bandwidth, and beam is lower than thecurrent one.

A WTRU may receive RCI from one or multiple WTRUs associated with itsgroup. If the WTRU receives more than a predetermined or configurednumber of RCIs from different WTRUs, each indicating that the groupsubresource was not able to meet latency requirements, the WTRU mayperform resource reselection for the group resource. The WTRU mayutilize the latency requirements of the other WTRUs in the RCI toschedule the group resource.

The WTRU may be configured to echo a received resource reservationsignal under one or more of the following conditions. The WTRU may echothe received resource reservation signal if it is configured to do so bythe application layer, either explicitly or implicitly (e.g., throughthe configuration of a member ID which has some specific value and everyN member IDs performs echoing). The WTRU may echo the received resourcereservation signal if the received value of the group SCI transmitted bythe designated WTRU or any group RCI corresponding to the WTRU's grouphas a quality (e.g., RSRP) below a threshold. The threshold may dependon the PPPP/PPPR of the transmissions allowable for the group.

The above method may be advantageous to use in a single WTRU schedulingsubresources for multiple WTRUs in subsequent subframes. If the distancebetween different WTRUs in a group is large, other WTRUs in the vicinityof the group may not be able to detect the initial SCI transmission andmay select resources that collide with the group resource. Repeating(i.e., echoing) the group resource may avoid such resource collision byother WTRUs performing resource selection.

Referring now to FIG. 2, a diagram illustrating a first method of groupreservation using subresource coordination is shown. In this method, anSCI may schedule transmission for a single WTRU. A first WTRU 202 maytransmit a first SCI 202 or resource reservation signal to scheduletransmissions for itself in a first reservation period 206. Forwardbooking in the SCI 204 for a specific resource reservation period may beused to reserve resources for transmissions by other WTRUs in the group.The first WTRU 202 may transmit a group reservation using the SCI 204,or equivalent sidelink scheduling message, in combination with a firstRCI 208. The first RCI 208 may be transmitted as a MAC CE on the PSSCH.

The first WTRU 202 may set the contents of the SCI 204 to indicateresources 210 being scheduled by the first WTRU 202. The first WTRU 202may indicate a forward booking indication depending on whether the sameresources are reserved in a future reservation period. The SCI 204 mayinclude a group identifier field. The first WTRU 202 may set this fieldto the group ID of the group for which resources are being reserved. Thescheduling information in the SCI 204 may indicate the specificresources reserved in the scheduling information. The resources 210 maybe one or a set of subframes/slots and resource blocks within eachsubframe/slot. The first WTRU 202 may include the first RCI 208 in itsown transmissions in the resources indicated by the first SCI 204. Thefirst RCI 208 may be sent as a MAC CE multiplexed with the first WTRU's202 transmissions on PSSCH. The first RCI 208 may include an indicationof whether or not the first WTRU 202 intends to utilize the sameresource (reserved by the first SCI 204) in a next reservation period212 and/or the sequence of WTRUs which should utilize the groupresources in the next reservation period 212. As shown in FIG. 2, thefirst WTRU 202 may use the first RCI 208 to indicate that a second WTRU214 should transmit in the resources in a second reservation period 212.

The first WTRU 202 may include the entire sequence of WTRU IDs so thatthe second WTRU 214 may know its own turn in the sequence oftransmissions based on the WTRU ID of the last group reservation signaland this sequence. The second WTRU 214 may be a member of the same groupand may decode the first SCI 204 containing the group ID and read theMAC CE. The second WTRU 214 may transmit in the same resources in thesecond reservation period 212 if it determines it is the next WTRU inthe sequence (i.e., the resource is assigned as a transit resource forthis WTRU). Otherwise, the second WTRU 214 may only receive thetransmissions in the next reservation period and/or decode the first RCI208.

The second WTRU 214 may transmit a second SCI 216 schedule the resourcesin the second reservation period 212. The second WTRU 214 may also senda second RCI 218 in its own transmissions in the resources indicated bythe second SCI 216. As shown in FIG. 2, the second WTRU 214 may use thesecond RCI 218 to indicate that a third WTRU (not shown) should transmitin the resources in a third reservation period.

Referring now to FIG. 3, a diagram illustrating a second method of groupreservation using subresource coordination is shown. In this method, anSCI may schedule transmissions for multiple WTRUs in a reservationperiod. Single WTRUs may be assigned a subresource of the SCI scheduledresource. Forward reservation may be used to reserve subsequentresources for the WTRUs in the case of periodic transmissions by thegroup.

A first WTRU may transmit a group reservation signal using a first SCI302 and a first RCI 304, for example, using the PSSCH. The first WTRUmay include scheduling information, group ID, and forward bookingsignals in the first SCI 302 for a first reservation period. The firstWTRU may also transmit a formatting or indication of the subresourceswithin the first reservation period 308. More specifically, the firstWTRU may provide an indication of the size and location of eachsubresource in the resource reserved by first SCI 302. The firs WTRU maytransmit data destined for the indicated group in the first subresource306 indicated by the first SCI 302. In addition, the WTRU may transmitthe first RCI 304 in a MAC CE using this first subresource 306. The MACCE may contain the sequencing of member WTRU ID transmissions to be usedwithin the subresources. Each subresource may be used for thetransmission of data from a single WTRU associated with the group. AWTRU that receives the first SCI 302 may determine the subresourcestructure and decode the first subresource 306.

Based on the contents of the first RCI 304 transmitted in the firstsubresource 306, the WTRUs in the group may determine their ownsubresources. The WTRUs may transmit data associated with the group intheir own subresources. For example, a second WTRU may transmit data ina second subresource 310 in the first reservation period 308. A thirdWTRU may transmit data in a third subresource 312 in the firstreservation period 308. A fourth WTRU may transmit data in a fourthsubresource 314 in the first reservation period 308. A WTRU may transmitusage information using its on RCI. For example, the fourth WTRU maytransmit a second RCI 316 indicating its resource usage information.

If a WTRU does not have data to transmit associated with the group, itmay transmit an RCI indicating it will not need the resource in the nextreservation period. This information may be used by the initiator of theRCI (e.g., a designated WTRU) to determine the schedule for the nextreservation period, or to determine whether the group resource needs tobe reserved at all for the next reservation period.

A WTRU that transmits the group reservation signal may determine theneed for reserving group resources in a future reservation period basedon the transmissions of RCI or control information in each of thesubresources of a previous reservation period. More specifically, a WTRUmay decode the RCI or similar control information from each WTRU in eachof the subresources of a reservation period. Based on this information,the WTRU may determine whether to keep or not, the resources for thenext reservation period. The determination may be based on one or moreof the following: the number of WTRUs that still have data to transmitassociated with the group; the buffer occupancy of each WTRU in the RCI;the detected RSSI, RSRP or similar in each of the subresources in theprevious reservation period; and a random number of reservation periods,potentially chosen at the first transmission of the group reservationsignal associated with the specific resources, and which is decrementedat each transmission of the reservation period associated with the sameresources.

If the WTRU decides to keep the resources based on the above conditions,the WTRU may transmit a resource reservation signal associated with thesame resources in the next reservation period. Alternatively, based onthe above information, the WTRU may decide to perform a reselectionprocedure to reserve a different set of resources, possibly with largeror smaller size, and possibly to accommodate the other WTRUs in thegroup based on the information sent in their RCI. Alternatively, theWTRU may decide to reserve the same or a different set of resource butfor use by a subset of the WTRUs in the group, possibly those that stillhave data to be transmitted. The WTRU may also decide to not reserve anyresources in the reservation period, and not transmit any groupreservation signal if, for instance, none of the WTRUs have data pendingin their buffers.

A WTRU configured to transmit a group reservation signal may select arandom number between n1 and n2, and may transmit a group reservationsignal with a forward booking indication set. Upon transmission of eachresource reservation signal, the WTRU may decrement the random number.When the random number reaches 0, the WTRU may perform a resourcereselection procedure for the group resources as long as the WTRU stillhas data in its buffers and at least n WTRUs in the group have at leastx bytes of data in their buffers associated with group communication.The WTRU may decide to keep the existing resources in the nextreservation period if the counter has not reached 0 and at least y ofthe WTRUs in the group have indicated that they still have at least xbytes of data in their buffers associated with group communication. Inaddition, the WTRU may change the RCI for transmission of the next groupreservation signal to change the set of WTRUs that have an assignedsubresources and the size of the subresources based on the RCIinformation received from each WTRU.

A WTRU may implicitly or explicitly associate a subresource within theset of resources indicated by the resource reservation signal to be usedfor its own transmissions. A WTRU may determine to use a specificsubresource within the resources indicated in a reservation signal basedon one or more of the following: an explicit mapping based on ID orsimilar identification; sequencing information, such as RCI transmittedby a WTRU, the network, or the application layer which may betransmitted in either the PDCCH or the PDSCH; priority of data to betransmitted, including delay requirements of the data; arrival time ofthe data to be transmitted; range of data to be transmitted; previoustransmissions by other WTRUs in the same subresource (e.g., during aprior reservation period, or prior transmission of reservation signal);measured RSRP, RSSI, or CBR associated with the subresource during aprior reservation period or associated with priori transmission of thereservation signal; distance from or relation to the WTRU thattransmitted the resource reservation signal; and validity, from theperspective of the transmitting WTRU, of the sensing results used by theWTRU which performed the resource selection.

A WTRU may determine the subresource in which it can send its owntransmissions based on an identifier assigned to it, such as a groupmember ID. For example, the WTRU may determine that it can use thei^(th) subresource if its group member ID modulo N=i.

A WTRU with pending transmissions associated with a group identifier maydetermine the subresources associated with its own transmission withinthe set of resources reserved for the group using resource coordinationinformation (RCI).

A WTRU may determine its transmission subresource based on RCI undercertain conditions associated with the sensing results used by the WTRUwhich performed the resource selection and/or transmission of theresource reservation signal. More specifically, a WTRU may use itstransmission subresource indicated in RCI if and only if its own sensingresults indicate the availability of its transmission subresource.

A WTRU may use its transmission subresource if and only if the receivedquality of the reservation signal is above a threshold.

A WTRU may use its transmission subresource if the distance to the WTRUwhich transmitted the resource reservation signal does not exceed athreshold. In such case, the RCI or the resource reservation signal maycontain the geolocation of the WTRU that transmitted the resourcereservation signal.

If a WTRU is not able to use its subresources in the resources indicatedby the reservation signal and/or RCI, the WTRU may initiate its ownresource reservation procedure (sensing and resource selection) and/orre-transmit the resource reservation signal, possibly using its ownsubresources, or using a predefined subresource for that purpose.

A WTRU may determine the coordination of a group resource (i.e., when totransmit within a resource reserved for a group) based on configurationof an ordering from the application layer. More specifically, the WTRUmay receive a member ID, member index, or similar index that indicatesits sequence within the group. The sequence may dictate when and inwhich subresource the WTRU may perform its own transmission.

A WTRU may receive a group member index of N and determine that itshould transmit in the N^(th) subresource associated with a groupreservation. The N^(th) subresource may be determined in both time andfrequency spaces. For example, the SCI may designate x subchannels overy consecutive slots, and further indicate a subresource to correspond toa single subchannel. The WTRU may then determine the Nth subresource byindexing (first by subchannel in a given slot) and continuing theindexing of the subchannels in the next slot, until the N^(th)subresource is reached.

A WTRU may determine the timing of its own transmissions based on itsmember index as well as the member index transmitted by other WTRUs inthe same group in the reservation signal. For example, a WTRU withmember index N may transmit in the same resource that occurs oneresource reservation period after it detects a transmission for thegroup which contains a group member index of N-1 in the transmitted SCIor RCI.

A WTRU may further determine that it is the designated WTRU (i.e., itshould perform resource reservation for the other WTRUs) if itconfigured with a specific value of the member ID. For example, a WTRUwith member ID of 0 may determine that it needs to perform resourcereservation for the group of WTRUs. A WTRU that is configured withmember ID different than 0 does not perform group reservation and onlytransmits in its own subresource or according to the sequence indicatedby its member ID.

A WTRU may further determine it needs to perform echoing of thereservation signal based on its member ID. For example, certain memberIDs may be associated with the task of echoing the reservation signal(e.g., all even-numbered member IDs should perform echoing of thereservation signal). The determination of the need to perform echoingmay be based on both the member ID and the subresource configuration.For example, a WTRU may determine it needs to perform echoing if thesubresource configuration consists of x subresources in a given timewindow, and (member ID) (mod x)=0. In other words, the transmission ofone echoed reservation signal may be required every subresourceconfiguration window.

A WTRU configured to monitor sidelink transmissions for a resourcereservation signal may, upon reception of the resource reservationsignal associated with the group to which the WTRU belongs, treat theentire resource reserved by the reservation signal as a contention-basedresource. More specifically, the WTRU may perform transmission on theentire resource if it has data available for transmission. The WTRU maythen initiate a contention detection and/or contention resolutionprocedure following the transmission to determine whether its owntransmission collides with another WTRUs transmission. The procedure mayconsist of determining the measured RSCP in the shared resource duringtransmission on the shared resource. For example, a WTRU may perform anLBT procedure at the beginning of the reserved resource, and maytransmit in the reserved resource if the channel is deemed to be clear.

Referring to FIG. 4, a diagram illustrating a method of reservingcontention based resources is shown. A WTRU configured to monitorsidelink transmission for a resource reservation signal may, uponreception of the reservation signal associated with the group to whichthe WTRU belongs, transmit on a portion of the resource depending onwhether it detects another WTRU in the group already transmitting onthat resource. For example, a WTRU may be assigned a sequence number forthe starting subresource within a resource. The starting subresourceassociated with a specific WTRU may be determined by one or more of theWTRU member ID and the RCI. For example, the member ID may range from1-N, and the starting subresource for that WTRU would be given by theWTRU member ID. The RCI may be transmitted periodically, in the SCI, orin one of the subresources of PSSCH intended for transmission of theRCI.

A WTRU may determine whether it can transmit on the contention-basedresource by sensing the subresources occurring in time prior to its ownstarting subresource location. If the WTRU determines that the resourceis not occupied (e.g., the RSRP of each of the subresources is below athreshold), the WTRU may decide to transmit in the remainder of theresource, starting from the WTRUs own subresource. A subresource mayconsist of any of an OFDM symbol, slot, subframe or multiple subframes,and may be limited to a number of resource blocks in frequency(contiguous or non-contiguous). A subresource may or may not becontiguous in time. The subresources may themselves be contiguous ornoncontiguous in time, and may or may not be associated with the sameresource blocks. The format of the subresources, the number ofsubresources may be provided in one or more of the SCI, RRCconfiguration or preconfiguration, and the data transmitted in adeterministic subresource (e.g., in a MAC CE).

As shown in FIG. 4, an SCI 402 may schedule a set of subresources 404. Afirst WTRU having a first sequence number may be assigned a firststarting subresource 406 based on one or more of the methods describedabove. The first WTRU may not transmit on the first starting subresource406. A second WTRU, which may be assigned a second sequence number, maydetect that the first WTRU is not transmitting in the first startingsubresource 406 and may determine it may transmit in a second startingsubresource 408. However, the second WTRU may not transmit in the secondstarting subresource 408. A third WTRU, which may be assigned a thirdsequence number, may detect that the second WTRU is not transmitting inthe second starting subresource 408 and may determine it may transmit ina third starting subresource 410. The third WTRU may start transmittingin the third starting subresource 410. The third WTRU may transmitthrough the remainder of the set of subresources 404.

The procedures described above for use of reserved resources for a groupof WTRUs may be applied for use with network scheduled resources. Morespecifically, a group of WTRUs may use resources assigned by thenetwork. As described herein, a number of procedures may be added toenable the use of network scheduled resources by a group of WTRUs.

A WTRU within a group may receive a group RNTI (“Gr-V-RNTI”) forresource assignments usable by all WTRUs in a group. The RNTI may beassigned to a WTRU in dedicated RRC signaling. A WTRU may receive theRNTI from the gNB upon joining a V2X group. Alternatively, a WTRU mayrequest a group RNTI upon joining a group of WTRUs. For example, uponindication from upper layers that a WTRU has joined, should join, orshould form a group, a WTRU may request a group RNTI from the gNB usinga sidelink WTRU Information or similar RRC message. The WTRU may receivea group RNTI as part of the signaling to establish a unicast/multicastlink (e.g., a unicast link establishment request to the network or in anetwork initiated sidelink unicast link establishment message). The WTRUmay receive the group RNTI in dedicated configuration. The request for agroup RNTI may further contain the WTRU's group identification (asconfigured by application layer) for the gNB to identify the WTRU group.The WTRU may further derive the group RNTI from the destination ID(e.g., the L2 ID that identifies the unicast/multicast group). Forinstance, the WTRU may use the entire or the least/most significant bitsof the destination ID associated to the unicast/multicast link as thegroup RNTI. Alternatively, the WTRU may derive the group RNTI from thesource L2 ID of one or any of the WTRUs associated in theunicast/multicast link.

A WTRU may monitor PDCCH for a Gr-V-RNTI when configured by applicationlayers as being part of a group and when configured by the network toperform network scheduled V2X communication. A WTRU may not need tomonitor Gr-V-RNTI otherwise. A WTRU that joins multiple groups mayfurther be assigned different Gr-V-RNTI values associated to the groupsit has joined.

A V-RNTI of a designated WTRU may be used for all assignments by thenetwork of resources to be used for communication in a group of WTRUs. AWTRU may learn of the designated WTRU's V-RNTI from coordinationinformation (e.g., RCI) sent by the designated WTRU. Specifically, aWTRU, when becoming a designated WTRU for a group (e.g., when receivingan indication from the application layer) may transmit an RCI or similarcoordination information on sidelink to the other WTRUs in the groupincluding its network assigned V-RNTI.

A WTRU may monitor PDCCH using the V-RNTI of a designated WTRU whenconfigured by the application layer as being part of a group and whenconfigured by the network to perform network scheduled V2Xcommunication. A WTRU may not need to monitor the designated WTRU'sV-RNTI otherwise.

A WTRU may further request permission from the network to use adesignated WTRU's V-RNTI. For example, upon reception of a designatedWTRU's V-RNTI, a WTRU may send a request/indication to the networkbefore using the WTRU's V-RNTI and being allowed to transmit insubresources within the network assigned resources. A WTRU may furtherreceive an indication from the network whether the WTRU can or cannottransmit within resources assigned to the designated WTRU's V-RNTI.

A WTRU may transmit such request/indication to the NW regularly (e.g.based on some timer), or upon a change in the distance (based ongeolocation) to the designated WTRU's V-RNTI, change in the designatedWTRU for the group, or upon joining another group.

A WTRU that monitors a V-RNTI associated with another WTRU may furtherreceive an additional indication (e.g., a DCI) in a resource grant fromthe network. A WTRU may utilize the indication to distinguish a resourcegrant usable by a group vs a resource grant allocated only for use ofthe individual WTRU associated with the V-RNTI. The indication may takeon two values, group vs individual. A value of group indicates that theWTRU may utilize a subresource in the resources allocated using V-RNTI.A value of individual indicates that this is not permitted.

A WTRU may transmit within a subresource of a network allocated resourceusing the mechanisms described above for WTRU autonomous transmission,which may be based on transmission of RCI by one or multiple WTRUs. Inaddition, a WTRU may receive RCI from the network as part of an RRCmessage, MAC CE, DCI, or similar message transmitted by the gNB.

A WTRU may request semi-persistent sidelink resources usable for a groupof WTRUs. The WTRU may receive indication from the application layer toinitiate such a request to the network. More specifically, a WTRU mayprovide assistance information for requesting sidelink SPS resourcesthat reflect the resource requirements of a group of WTRUs. A WTRU mayaccount for the resource requirements of other WTRUs in a group whenrequesting SPS resources from the network, and/or when sending WTRUassistance information for SPS resources from the network. Morespecifically, the WTRU requesting the SPS resources may increase orscale the number of required SPS resources compared to its own resourcerequirements based on additional information. The additional informationmay include one or more of the following. The additional information maybe the number of WTRUs in the group, possibly provided by theapplication layer. The additional information may be a factor (e.g.,multiplier) compared to the WTRU's own periodicity of resources,possibly provided by the application layer and. The factor may representthe number of WTRUs in a group, the number of WTRUs in the group thathave a blocking relationship, the number of WTRUs that need to processand relay a message, or the number of duplications required for amessage to be broadcast to the entire group. For example, if a WTRUdetermines its periodicity of communication for a specific service is300 ms, and the application layer indicates a factor of 10, the WTRU mayrequest SPS resources with periodicity of 30 ms.

The additional information may be timing offset changes of SPSresources. The additional information may be QoS related information(e.g., priority) of the transmissions pending at the WTRU and intendedfor the group. The additional information may be range-relatedinformation, such as whether the data with pending transmissions thatinitiated the SPS request needs to be sent over long or short range. Theadditional information may be a frequency band of operation, such aswhether transmission between the group members is over high frequency(e.g., mmWave).

A WTRU may initiate a request for SPS sidelink resources by sending WTRUassistance information. If the WTRU is the designated WTRU of a group(e.g., as determined by the application layer), the assistanceinformation may be based on the WTRU's own resource needs as well aspotential resource needs of other WTRUs. A WTRU may request a shorterperiod SPS (e.g., by a factor x) compared to its own SPS period. Thefactor x may be received from the application layer or it may bededuced/derived from information provided by the application layer.

A WTRU may determine the need for the periodicity of its own packetarrivals to be scaled, and an amount by which it should be scaled, inits request for SPS resources. This may be based on topology (e.g., thenumber of vehicles that may be in a position of blocking, as indicatedby upper layers), frequency band (e.g., scaling may be required whentransmission is on mmWave), and QoS (e.g., scaling may be requireddepending on priority or reliability of the packets received from higherlayers).

A WTRU may use one or more of the following rules to determine whetherits own packet periodicity needs to be scaled before requesting SPSresources with a specific periodicity. Scaling may be performed iftransmitting on mmWave and using beam angle<x. Scaling may be performedif priority of the packets associated with periodic transmission ishigher than a certain value. If scaling is to be performed based on oneor more of the above determinations, the scaling may be by the factorprovided by application layer.

A WTRU may determine the specific time/frequency resource it may use totransmit data intended for a specific group based on one or more of thefollowing criteria. The WTRU may use RCI or similar informationtransmitted by another WTRU over sidelink or by the network to determinethe time/frequency resource. For example, sequencing information forresource usage among the WTRUs may be contained in RCI. The WTRU may usetiming of data arrival with respect to the specific resource todetermine the time/frequency resource. For example, a WTRU may assumethe resource having the smallest latency compared to the arrival of thepacket may be used for transmission of the packet. For example, the WTRUmay use the next single resource in time in the SPS grant which followsthe arrival of the packet to the AS layer.

The WTRU may use the WTRU ID within a group assigned by applicationlayer or network to determine the time/frequency resource. A WTRU havinggroup WTRU ID M may transmit in the Mth (Mod n) resource in time of anSPS grant following reception of the grant. The values of M and n may beprovided by higher layers.

In addition, the WTRU may use the priority of data to be transmitted,including delay requirements of the data, the arrival time of the datato be transmitted, the transmission range of data to be transmitted,previous transmissions by other WTRUs in the same subresource, andmeasured RSRP, RSSI, or CBR associated with the subresource or othersubresources, possibly during a prior reservation period, to determinethe time/frequency resource.

Based on SA1 requirements, the AS may be able to control thecommunication range for a message based on the characteristic of themessage transmitted by a WTRU. These characteristics may be determinedby the application layer and may be related to the type of applicationlayer message (e.g., intended for the entire group of WTRUs, or intendedfor a single WTRU in a group). To ensure resource efficiency, a WTRU mayset its transmission parameters to assume the worst case transmissionrange, such as transmission from the head of the group to the tail ofthe group, or considering the worst case group length, assuming WTRUs ina group follow each other in a longitudinal fashion on the road.

A WTRU may receive one or more parameters associated with the range of amessage to be transmitted from the application layer. In this context,the term “range” may refer to the distance to be reached by a WTRU'stransmission, or a distance over which reliable transmission may beensured. The one or more parameters may be associated with the QoS ofthe packet to be transmitted. The one or more parameters may be providedwith each packet received from the higher layers (e.g., “per packet”range). Alternatively, the WTRU may receive a range requirement QoSparameter associated with a specific destination address and/or upperlayer flow and/or bearer and may assume the same range to be applicableto all packets received having the same destination address/flow/bearer.Alternatively, the range requirement may be derived implicitly fromother parameters provided by the upper layers such as a specific QoSparameter, or the destination address (e.g. multicast vs groupcast).

The one or more parameters associated with range may take a finitenumber of values. Each value may further be associated with any of thefollowing parameters. The value may be associated with a specificphysical distance of transmission using a single sidelink transmissionThe value may be associated with a specific physical distance oftransmission assuming relayed sidelink transmission. The value may beassociated with a physical transmission direction and/or coveragecorresponding to whether the packet needs to be transmitted to vehiclesbehind the said WTRU, both behind and in-front of the said WTRU, in alldirections around the said WTRU.

The one or more parameters associated with range may alternatively takeon a finite number of values with a qualitative association, forexample, short range, medium range, and long range.

A WTRU may change or adapt one or a number of transmission parametersfor a packet based on the received range value associated with thatpacket. The range value may be further derived from a QoS characteristicassociated with the packet (e.g., through a configured table). Forexample, a QoS value x may indicate a specific entry in a table and thatentry in the table may be further associated with a specific value ofrange requirement. Range requirements may take on any number of distinctpossible values (e.g. 1-x, or low/medium/large, ect). This adaptationmay allow the WTRU to achieve the required range for V2X transmissionwithout having to assume worst-case transmission parameters required forall V2X transmissions.

The WTRU may associate one or more range values with a specific unicastor multicast link. More specifically, the WTRU may associate one or morerange value with one or more of the following: a destination ID, aunicast/multicast link ID (either determined by the WTRU, from upperlayer, or provided by the network), a logical channel, radio bearer, orgroup thereof, a QoS flows or group of QoS flows. The WTRU may make theassociation at one or more of the following times: at creation of alogical channel or radio bearer, at the initiation, by the upper layers,of a unicast/multicast link with one or more WTRUs, and during signalingwith the network for establishing a unicast/multicast link with one ormore WTRUs.

The WTRU may receive an association from the upper layers or from thenetwork. More specifically, the WTRU may receive an indication from theupper layers to initiate a unicast/multicast link with a specificdestination ID and/or unicast/multicast link ID. The WTRU may beprovided an associated QoS value (e.g., VQI) from which the WTRU mayderive a range. The WTRU may then apply the transmission parametersapplicable to the range values for each packet it receives from upperlayers having the specific destination ID or unicast/multicast link ID.

A WTRU may receive the association of range value to TX parameters fromthe network. More specifically, a WTRU may initiate signaling with thenetwork for establishment of a unicast/multicast link, and may furtherprovide the associated range values applicable for thisunicast/multicast link. The network may respond with the applicable TXparameters to be applied to transmit parameters associated with thislink. Packets may be associated with a destination ID, logical channel,etc. as described above.

The WTRU may determine the applicable transmission parameter to modifyand the specific values to assign such parameter based on one or more ofpreconfiguration and network configuration.

The WTRU may modify one or more of the following transmission parametersbased on the range values or range parameters received from theapplication layer: number of retransmissions on PSCCH and/or PSSCH,selected resource pool, the min/max/average number of resources selectedby the WTRU, use of TX diversity, TX Power on PSCCH and/or PSSCH,selected MCS for transmission, beamforming characteristics (e.g.,whether to turn on/off beam forming, beam angle to use, whether totransmit on one or multiple beams, and which beam directions to transmiton relative to another WTRU's transmission), and whether toenable/disable relaying.

The WTRU may select one or a set of values of any of the abovetransmission parameters based on the range values associated to thattransmission.

A WTRU may also determine the applicable value or values of a giventransmission parameter based also on other measured aspects of thechannel, such as one or more of the following: measured CBR on a set ofresources, measured CR at the WTRU, quality of a reference signaltransmitted by the network or another WTRU, HARQ feedback from anotherWTRU, CQI measurements from another WTRU, and measured path loss betweena WTRU and one or more other WTRUs (e.g., those involved in theunicast/multicast link).

A WTRU may be configured to maintain path loss estimates and/or channelquality estimates over a unicast link with a paired WTRU (e.g., bymeasurement of a reference signal transmitted by the paired WTRU). TheWTRU may be configured with a set of applicable values for TX power onPSCCH and/or PSSCH for each combination of measured path loss and/orchannel quality and range value. The WTRU may receive a packetassociated with a destination address which has a range value tied toit. The WTRU may then select the allowable TX power values fortransmission of that packet based on the range parameter and the pathloss and/or channel quality over the link with the paired WTRU (on theunicast link). The WTRU may further adapt the TX power over theallowable range based on the measured CBR of the channel.

A WTRU may receive a packet from the application layer marked as eithershort range, medium range, or long range. A WTRU may select a specificMCS value, or select from a subset of allowable MCS values for a shortrange packet, select a different MCS, or select from a different subsetof allowable MCS values for a medium range packet, and likewise for longrange packet.

A WTRU may receive a packet from the application layer marked as eithershort range, medium range, or long range. A WTRU may use a beam angle ofx1 for short range packets, a beam angle of x2 for medium range packet,and a beam angle of x3 for long range packet when transmitting thepacket over the air. A WTRU may receive a packet from the applicationlayer with a range parameter value which indicates that the packetrequires transmission only to a single direction. The direction may befurther specified (e.g., using cardinal directions or relative to avehicle's heading). The WTRU may decide to transmit the packet only on asingle beam or subset of beams associated with the indicated direction.Alternatively, a different packet may indicate transmissions in alldirections. The WTRU may decide to transmit the packet in all beams inthis case.

A WTRU may be configured with a TX power offset value, a maximum TXpower, or a TX power computation formula for each of the range parametervalues that can be configured by the application layer. The WTRU MAC mayindicate the appropriate TX power offset value, maximum TX power, orcomputation formula to the PHY layer when the MAC PDU is sent to the PHYlayer for transmission. The PHY layer may then apply the associatedoffset/maximum/formula to the TX power calculation when transmitting theMAC PDU.

The range parameter associated with a transport block provided to thePHY layer may consist of the range associated with the worst case (i.e.,largest range) packet that may be multiplexed onto that transport block.

A WTRU may estimate side link path loss values based on the sensingresults. The WTRU may process a set of such side link path lossestimates and determine a side link path loss range corresponding to theset of configured range by associating the configured small, medium andlong range with an estimated path loss. For example, the WTRU mayassociate a 33-percentile path loss estimate with the small range,67-percentile path loss with the medium range and 100-percentile withthe large range. The WTRU may determine a side link power based on theside link path loss estimate associated with the configured range. Toenable the path loss estimate, a WTRU may indicate transmit power in theSCI information.

A WTRU may be configured with a set of transmission characteristics toassociate to each value of range parameter received from the upperlayers. For example, the range parameter value from the upper layers maytake on a set of predefined values (1, 2, . . . N). For each value ofthe parameter, the WTRU may be configured to assign a desired N-tuple oftransmission parameters, where each element in the N-tuple consists ofone of the above-mentioned transmission parameters, such as N-tuple,number of retransmissions, TX power, selected MCS, and beamformingangle. The WTRU may be configured with a table mapping of rangeparameter to a distinct N-tuple. A WTRU may further be allowed toperform selection of any or a subset of possible values for one of theN-tuples. For example, the WTRU may have no preference for TX power orit may be or selectable by the WTRU. Beam angle may be a selection froma subset of allowable/supported beam angles for a certain rangeparameter value.

A WTRU may be configured with the set of applicable transmissionparameters by means of a transmission profile. The transmission profilemay consist of a set of transmission parameters to be applied to atransmission on sidelink. The WTRU may select, based on characteristicsof the data to be transmitted, such as its transmission range and/or QoScharacteristics (e.g., priority or reliability) associated with thedata, to perform transmission using an associated transmission profileconfigured for that transmission range and/or QoS characteristic. TheWTRU may use a first transmission profile for transmission of packethaving a first range characteristic, and it may select a secondtransmission profile for transmission of a packet having a second rangecharacteristic.

A transmission profile may be configured by the gNB (e.g., through RRCsignaling), it may be preconfigured, or it may be hardcoded in the WTRUby specification. The WTRU may further support a subset of hardcoded anddefined transmission profiles and may indicate the supportedtransmission profiles to the gNB and/or upper layers.

The transmission profile may influence one or more of the following WTRUtransmission parameters. The transmission profile may dictateretransmissions on PSCCH and/or PSSCH. For example, a transmissionprofile may be associated with a number of retransmissions (e.g., ofSCI) to be applied on PSCCH and/or PSSCH. The transmission profile mayalso dictate the time/frequency relationship between transmissions andretransmissions. For example, the time between transmission andretransmission may be fixed and determined by the transmission profile.The channel (or frequency location) of the retransmission may have arelationship to the frequency resource used by the initial transmission,where that relationship may be determined from the transmission profile.

The transmission profile may influence the selected resource pool. Forexample, a transmission profile may restrict or dictate the resourcepools that can be used for transmission of data via sidelink.

The transmission profile may influence the use of TX diversity. Forexample, a transmission profile may indicate whether TX diversity (e.g.,space diversity) should be applied to transmission of the data Atransmission profile may further configure the settings of diversitytransmission (e.g., through hopping of resources) by configuring thehoping pattern across slots, beams, resources, BWPs, and TX pools.

The transmission profile may influence the TX Power on PSCCH and/orPSSCH. The transmission profile may determine the nominal or maximumtransmission power to be used. It may also indicate the amount by whichthe transmission power can be increased/decreased with each initialtransmission/retransmission and/or successfultransmission/retransmission.

The transmission profile may influence the selected MCS fortransmission.

The transmission profile may influence beamforming characteristics. Thetransmission profile may determine or influence the beamformingcharacteristics for transmission. The characteristics may includewhether to perform omni-direction transmission or transmission over onlya subset of beams. whether to turn on/off beam sweeping, and the beamangle or set of beams to use. The set of beams may reference a specificreference direction, such as the direction of travel of a vehicle orsome fixed direction (e.g., north).

The transmission profile may influence enabling/disabling relaying. Thetransmission profile may indicate whether a transmission should betransmitted to a relay or not. A WTRU, based on the transmissionprofile, may further indicate within the transmission (e.g., as acontrol element in the PDU of one of the AS layers such as MAC, RLC,PDCP) whether or not a specific message should be relayed, and with howmany hops.

The transmission profile may influence sidelink transmission mode. Thesidelink transmission mode may determine whether the WTRU employs PC5transmission or Uu transmission, whether the WTRU uses mode 3 or mode 4for the transmission, and/or whether the WTRU selects resources thatallow sharing between gNB scheduled and WTRU autonomous or resourcesthat are not shared.

The transmission profile may influence the bandwidth and carrierfrequency to use (e.g., indication of the bandwidth part or carrier).For example, the transmission profile may indicate the BWP to beutilized for the transmission.

The transmission profile may influence the control channel and/or datachannel format, (i.e., slot/mini slot format) and set of OFDM symbols touse in time/frequency. For example, the WTRU may be configured totransmit SCI or data using different PSCCH or PSSCH formats. The profilemay further determine which of the allowable control channel formats touse for PSCCH and/or PSSCH.

The transmission profile may influence resource selection criteria forone-shot or periodic resources. A transmission profile may influence oneor more criteria of the mode 4 (WTRU autonomous) resource selectioncriteria. For example, each transmission profile may be associated witha different RSRP/RSSI/CBR or similar threshold to determine whether aresource is occupied by another WTRU transmission or is available forselection. Each transmission profile may be associated with a differentcriteria (e.g., maximum number of consecutive resources to be reservedor criteria for reselection of resources) for reserving or maintainingthe selected resources.

A WTRU may be configured with multiple transmission profiles and beconfigured to use different transmission profiles depending on the area.More specifically, the WTRU may determine its current geographicallocation, and apply the configured transmission profile for thatgeographical location.

The V2X application layer, or any of the upper layers as describedherein, at the WTRU may be aware of the transmission profiles supportedor configured at a given time, and may select a transmission profile fortransmission of a V2X message when it sends the message for transmissionby the AS layer. The application layer may provide an index to theselected transmission profile. For example, each transmission profilemay be associated with a different range index, and the applicationlayer may pass a range index to the lower layer along with the packet tobe transmitted.

The WTRU AS may be configured with a set of transmission profiles (e.g.,PF1, PF2, . . . PFN). The WTRU may further be configured by the gNB witha mapping of range parameter (e.g., short, medium, long, or range1,range2, . . . range n) to profiles. The configuration may be provided tothe WTRU by RRC signaling, by MAC CE, via SI, or by preconfiguration.When the application layer selects a specific range value to be usedwith a packet, the WTRU AS may then select one of the configuredtransmission profiles associated with that range value.

A WTRU may receive an association between a destination address, carrierfrequency, or similar parameter identifying the destination of the V2Xmessage, and the range over which to transmit the message. Theassociation may be in the form of a mapping between one or multipledestination addresses and/or carrier frequencies and/or bandwidth partsand a range value. The range value may be in any form described herein(e.g., short, medium, long, directional information, etc.). The mappingmay be provided through configuration (e.g., pre-configuration orgNB/eNB configuration) or may be provided by upper layer configuration.The mapping may also be altered by an updated configuration. The WTRUmay apply a certain transmission parameter or set of transmissionparameters during transmission of a V2X packet with the specificdestination address at any time based on the mapping of destinationaddress to range mapping.

The WTRU may maintain the mapping of destination address to range (e.g.,short, medium, long) received by the gNB by RRC signaling. The WTRU maymaintain such mapping until it receives a new mapping upon reception ofa new RRC configuration. The WTRU may also apply or assume a defaultrange (e.g., long range) for any destination addresses received fromupper layers which have not been configured with a corresponding rangevalue. Upon reception of a packet with a given destination address, theWTRU may apply a transmission parameter that meets the associated rangecharacteristics. The determination may be further based on atransmission profile, as described herein.

A WTRU may be configured with and maintain an association between adestination address, carrier frequency, or similar parameter identifyingthe destination of the V2X message and a transmission profile. The WTRUmay receive this configuration from the gNB/eNB, from the upper layers,and/or in preconfiguration. Upon reception of a packet with a givendestination address, the WTRU may apply the associated configuredtransmission profile in order to transmit the packet.

The WTRU may have a two stage mapping from destination address totransmission profile to set of transmission parameters. Each stage ofthe mapping may be configured/reconfigured by differententities/mechanisms or at different times. The WTRU may be configured bygNB/eNB and/or pre-configuration with a mapping of profilenumbers/indices to transmission parameter sets. The transmissionparameter sets may consist of the setting of any of the parametersassociated with the transmission profile. The WTRU may then receive amapping from the application layer of destination address totransmission profile, such as in the form of an index in a set of knowntransmission profiles (e.g., PF1, PF2, PF3, etc). For example,destination address x may use transmission profile PF1.

A WTRU may provide a mapping of destination address to range indexand/or transmission profile to the gNB. The mapping may allow the gNB toperform appropriate scheduling decisions for mode 3 type operation(i.e., gNB scheduled). For example, a WTRU may provide a list ofdestination addresses to the gNB in an RRC message similar to theUESidelinkInformation message. The message may contain range informationassociated with each of the destination addresses. The WTRU may providethe range index associated with each destination address, as provided bythe application layer in the WTRU. The WTRU may provide the mapping ofdestination address to range index to the gNB at one or more of thefollowing events.

The WTRU may provide the mapping of destination to range index at achange of the mapping initiated by the WTRU's application layer,possibly as a result of receiving new mapping information from the V2Xcontrol function or any other network function in the core network.

The WTRU may provide the mapping of destination to range index at atransition by the WTRU to RRC_CONNECTED, possibly if the mapping waschanged while the WTRU was operating in RRC_IDLE/RRC_INACTIVE.

The WTRU may provide the mapping of destination to range index athandover for the case of a WTRU performing sidelink transmission whilein RRC_CONNECTED.

Further the WTRU may provide the mapping of destination to range indexat a RAN area update or tracking area update, during selection of a newPLMN by the WTRU (i.e., change of PLMN), and when the WTRU changes thegeographic area that may be preconfigured in the WTRU.

A WTRU may assign a distinct set of logical channels to packets with aspecific range parameter value. For example, logical channel IDs L1-L2may be used for packets marked as “short range,” logical channel IDsL3-L4 may be used for packets marked as “medium range,” and logicalchannel IDs L5-L6 may be used for packets marked as “long range.” TheWTRU may select the specific logical channel ID within the allowable setfor a specific range value based on other QoS-related factors (e.g.,priority). Namely, the WTRU may select the logical channel ID with thesmallest value within the set for “medium range” for a high prioritypacket to be set over medium range. The allowable sets may also beconfigured by the network or may be preconfigured in the WTRU.

A WTRU may mark an SDU with a specific range identifier value at the ASbased on the range parameter value. The range identifier value to rangeparameter value mapping may also be configurable. The WTRU may notrestrict a packet with a specific range identifier value to use aspecific logical channel. Instead, the WTRU may take into account therange parameter value/identifier in the L2 processing at PDCP, RLC, andMAC layers. For example, during segmentation of an SDU, a WTRU mayassociate the specific range identifier value or range parameter valueto each of the segments of the SDU.

A WTRU may perform concatenation/multiplexing of SDUs at any layer(e.g., RLC and/or MAC) such that two packets with different rangeparameter value are never concatenated/multiplexed. Alternatively, theWTRU may perform multiplexing between different logical channels suchthat the logical channel set associated with different range parametersare never multiplexed together.

A WTRU may perform selective concatenation/multiplexing of packetsand/or logical channels depending on the range parameter itself. Forrange parameter x, multiplexing may be allowed, while for rangeparameter y, multiplexing may not be allowed. For a range parametervalue associated with transmission direction, the WTRU may performconcatenation/multiplexing. For a range parameter associated to TXpower, the WTRU may not perform concatenation/multiplexing. These rulesmay be specified or configured to the WTRU by RRC or preconfiguration. AWTRU may further select a resource/grant for a PDU that is identified tobe restricted with a specific range based on a range associated withthat PDU. The range may be the worst case range.

A WTRU may determine the transmission parameters to be used for a MACPDU that contains logical channels or packets having different rangeparameter values. The determination may be based on specific rulesdepending on the range parameter value. More specifically, when the WTRUreceives multiple range parameters for a given packet, the WTRU may beconfigured with a specific behavior for each range parameter. The WTRUmay be configured to use a combination/sum. For example, if packetsassociated with different transmission directions are multiplexed, theMAC PDU may be transmitted in each of the directions associated with thedifferent range parameter values in that packet. The WTRU may beconfigured to use maximum transmit power. For example, if packetsassociated with different TX power are multiplexed in a MAC PDU, the MACPDU may be transmitted with the maximum TX power associated with any ofthe parameter values provided in the packet.

The WTRU may be configured to use a minimum beam angle. For example, ifpackets associated with different beam angle are multiplexed in a MACPDU, the MAC PDU may be transmitted with the minimum beam angleassociated with any of the parameter values provided in the packet. TheWTRU may be configured to use an average value of the above parameters.

A WTRU may also alter the rules associated with parameter selection(e.g., using an average value instead of a maximum value) depending onresource selection criteria. The resource selection criteria mayinclude, but is not limited to currently measured CBR, percentage ofcurrent availability of resources or intermediate resource availabilityfrom sensing results, and average RSSI of available resources.

A WTRU may include information associated with the range in the sidelinkbuffer status reports to the gNB. The range information may be providedexplicitly. The WTRU may provide an amount of data in the WTRU buffersassociated with each range parameter value. For example, for a rangeparameter that can take on “short,” “medium,” “long,” the WTRU mayreport an amount of data in the buffer for each of these three values.

A WTRU may provide this information implicitly using mapping, possiblyconfigurable, to the reported logical channel group. For example, a newset of logical channel groups may be reported. Each logical channelgroup may be associated with one or set of range parameter values. Themapping between range parameter value and logical channel group mayfurther be configurable. For example, a LCG may be mapped to one or morePPPP and one or more range parameter values. The WTRU may report thebuffer status associated with each LCG by determining the number ofpackets in the WTRU buffers associated with the configured PPPP valuesand range parameter values.

A WTRU may report a single range parameter value to the network for eachLCG reported. The single parameter value per LCG may be derived similarto the transmission parameter selection for multiplexed MAC PDUsdescribed above. More specifically, the single parameter value may be acombination, maximum, minimum, or average. For example, the WTRU maydetermine all the different beam directions of the packets in each ofthe logical channels associated with an LCG and with data pending inthose logical channels. The WTRU may report this set of beam directionsalong with the buffer status for that LCG. The set of beam directionsmay be mapped to a specific number (identifier) by configuration orstandardized mapping.

Data available at the PHY layer may be marked with a different resourcecharacteristic depending on the range parameter identifier describedabove. A WTRU may perform independent resource selection procedures foreach independent range parameter identifier provided above. Eachresource selection procedure may have specific rules dependent on theassociated range parameter identifier it is associated with. Inaddition, the WTRU may perform resource selection for a first value ofrange parameter first, and a second resource selection for a secondvalue of range parameter second.

A WTRU may perform resource selection for data requiring a giventransmit direction differently than another transmit direction.Specifically, the WTRU may only consider certain resources forsensing/resource selection.

Referring to FIG. 5, a flowchart illustrating the first method of groupreservation using subresource coordination is shown. In step 502, a WTRUmay receive a first SCI element from a second WTRU within a group. Instep 504, the WTRU may receive a first RCI element within a first set ofresources scheduled by the first SCI. The first RCI may includeinformation about which WTRU in the group is scheduled to use a secondset of resources. In step 506, the WTRU may determine, based on thefirst RCI, that one or more subresources within the second set ofresources are available. In step 508, the WTRU may transmit data in theone or more subresources.

Although features and elements are described above in particularcombinations, one of ordinary skill in the art will appreciate that eachfeature or element can be used alone or in any combination with theother features and elements. In addition, the methods described hereinmay be implemented in a computer program, software, or firmwareincorporated in a computer-readable medium for execution by a computeror processor. Examples of computer-readable media include electronicsignals (transmitted over wired or wireless connections) andcomputer-readable storage media. Examples of computer-readable storagemedia include, but are not limited to, a read only memory (ROM), arandom access memory (RAM), a register, cache memory, semiconductormemory devices, magnetic media such as internal hard disks and removabledisks, magneto-optical media, and optical media such as CD-ROM disks,and digital versatile disks (DVDs). A processor in association withsoftware may be used to implement a radio frequency transceiver for usein a WTRU, UE, terminal, base station, RNC, or any host computer.

1-20. (canceled)
 21. A wireless transmit/receive unit (WTRU) configuredfor sidelink communication, the WTRU comprising: a transceiver; and aprocessor, wherein: the processor is configured to receive a data packetfor transmission, wherein the data packet has an associated rangeparameter value; the processor is further configured to create asidelink radio bearer (SLRB) for the data packet having the associatedrange parameter value; the processor is further configured to select atleast one data transmission parameter based on at least the rangeparameter value; and the transceiver is configured to transmit the datapacket based on the selected at least one data transmission parameter.22. The WTRU of claim 21, wherein the data packet is associated with aquality of service (QoS).
 23. The WTRU of claim 21, wherein the datapacket is received from a higher layer.
 24. The WTRU of claim 21,wherein the range parameter value corresponds to a physical distance.25. The WTRU of claim 21, wherein the range parameter value indicates aphysical distance over which a quality of service (QoS) of the datapacket should be satisfied.
 26. The WTRU of claim 21, wherein the atleast one data transmission parameter comprises at least one of: amodulation and coding scheme (MCS), a transmission power, or a maximumnumber of retransmissions.
 27. The WTRU of claim 21, wherein the atleast one data transmission parameter is based on a network configuredmapping.
 28. The WTRU of claim 21, wherein the at least one datatransmission parameter is based on a CRB value.
 29. The WTRU of claim21, wherein the at least one data transmission parameter is based on alogical channel priority.
 30. The WTRU of claim 21, wherein the SLRB isbased on a network configuration, wherein the network configurationcomprises at least mapping information of the data packet to the SLRB.31. A method for sidelink communication, implemented by a wirelesstransmit/receive unit (WTRU), the method comprising: receiving a datapacket for transmission, wherein the data packet has an associated rangeparameter value; creating a sidelink radio bearer (SLRB) for the datapacket having the associated range parameter value; selecting at leastone data transmission parameter based on at least the range parametervalue; and transmitting the data packet based on the selected at leastone data transmission parameter.
 32. The method of claim 31, wherein thedata packet is associated with a quality of service (QoS).
 33. Themethod of claim 31, wherein the data packet is received from a higherlayer.
 34. The method of claim 31, wherein the range parameter valuecorresponds to a physical distance.
 35. The method of claim 31, whereinthe range parameter value indicates a physical distance over which aquality of service (QoS) of the data packet should be satisfied.
 36. Themethod of claim 31, wherein the at least one data transmission parametercomprises at least one of: a modulation and coding scheme (MCS), atransmission power, or a maximum number of retransmissions.
 37. Themethod of claim 31, wherein the at least one data transmission parameteris based on a network configured mapping.
 38. The method of claim 31,wherein the at least one data transmission parameter is based on a CRBvalue.
 39. The method of claim 31, wherein the at least one datatransmission parameter is based on a logical channel priority.
 40. Themethod of claim 31, wherein the SLRB is based on a networkconfiguration, wherein the network configuration comprises at leastmapping information of the data packet to the SLRB.